KVM-unit-tests - Revision history

Drjones at 17:43, 1 August 2020

2020-08-01T17:43:21Z

← Older revision		Revision as of 13:43, 1 August 2020
Line 7:		Line 7:

	The source code can be found at:		The source code can be found at:
	* https://gitlab.com/kvm-unit-tests/kvm-unit-tests		* https://gitlab.com/kvm-unit-tests/kvm-unit-tests.git
	</noinclude>		</noinclude>

Line 99:		Line 99:
	:: Run all tests on the current host		:: Run all tests on the current host
	<pre>		<pre>
	$ git clone https://gitlab.com/kvm-unit-tests/kvm-unit-tests		$ git clone https://gitlab.com/kvm-unit-tests/kvm-unit-tests.git
	$ cd kvm-unit-tests/		$ cd kvm-unit-tests/
	$ ./configure		$ ./configure

Drjones at 11:24, 1 August 2020

2020-08-01T11:24:45Z

← Older revision		Revision as of 07:24, 1 August 2020
Line 6:		Line 6:


	The source code can be found ~~on kernel.org's git server~~:		The source code can be found at:
	* https://~~git~~.~~kernel.org/pub/scm/virt/kvm~~/kvm-unit-tests~~.git~~		* https://gitlab.com/kvm-unit-tests/kvm-unit-tests
	* git://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests~~.git~~
	</noinclude>		</noinclude>

Line 100:		Line 99:
	:: Run all tests on the current host		:: Run all tests on the current host
	<pre>		<pre>
	$ git clone ~~git~~://~~git~~.~~kernel.org/pub/scm/virt~~/kvm/kvm-unit-tests~~.git~~		$ git clone https://gitlab.com/kvm-unit-tests/kvm-unit-tests
	$ cd kvm-unit-tests/		$ cd kvm-unit-tests/
	$ ./configure		$ ./configure

Drjones: /* API */

2020-01-21T14:14:13Z

API

← Older revision		Revision as of 10:14, 21 January 2020
Line 86:		Line 86:

	; Virtio		; Virtio
	: Buffer sending support (Currently virtio-mmio only)		: Buffer sending support. Currently virtio-mmio only.

	; Misc		; Misc

Drjones: /* Adding a test */

2020-01-21T14:10:44Z

Adding a test

← Older revision		Revision as of 10:10, 21 January 2020
Line 166:		Line 166:
	int main(int ac, char **av)		int main(int ac, char **av)
	{		{
	report("hello!"~~, true~~);		report(true, "hello!");
	return report_summary();		return report_summary();
	}		}
	</pre>		</pre>
Line 173:		Line 173:
	2. Ensure the appropriate makefile, e.g. x86/Makefile.common, has been updated by adding it to a tests variable<br>		2. Ensure the appropriate makefile, e.g. x86/Makefile.common, has been updated by adding it to a tests variable<br>
	<pre>		<pre>
	tests-common = $(TEST_DIR)/new-unit-test.flat		tests-common += $(TEST_DIR)/new-unit-test.flat
	</pre>		</pre>
	Note, the tests-common variable identifies tests shared between similar architectures, e.g. i386 and x86_64 or arm and arm64. Use the tests makefile variable of a specific architecture's makefile to build the test specifically for that architecture.		Note, the tests-common variable identifies tests shared between similar architectures, e.g. i386 and x86_64 or arm and arm64. Use the tests makefile variable of a specific architecture's makefile to build the test specifically for that architecture.
Line 179:		Line 179:
	3. You can now build and run the test		3. You can now build and run the test
	<pre>		<pre>
			$ ./configure
	$ make		$ make
	$ x86/run x86/new-unit-test.flat		$ x86/run x86/new-unit-test.flat

Drjones: /* Framework */

2020-01-21T14:02:55Z

Framework

← Older revision		Revision as of 10:02, 21 January 2020
Line 23:		Line 23:
	= Framework =		= Framework =

	The kvm-unit-tests framework supports multiple architectures; currently i386, x86_64, armv7 (arm), armv8 (arm64), ppc64, ppc64le, s390x. The framework makes sharing code between similar architectures, e.g. arm and arm64, easier by adopting Linux's configured asm symlink. With the asm symlink each architecture gets its own copy of the headers, but then may opt to share the same code.		The kvm-unit-tests framework supports multiple architectures; currently i386, x86_64, armv7 (arm), armv8 (arm64), ppc64, ppc64le, and s390x. The framework makes sharing code between similar architectures, e.g. arm and arm64, easier by adopting Linux's configured asm symlink. With the asm symlink each architecture gets its own copy of the headers, but then may opt to share the same code.

	The framework has the following components:		The framework has the following components:

Drjones: /* Framework */

2020-01-21T14:02:25Z

Framework

← Older revision		Revision as of 10:02, 21 January 2020
Line 23:		Line 23:
	= Framework =		= Framework =

	The kvm-unit-tests framework supports multiple architectures; currently i386, x86_64, armv7 (arm), armv8 (arm64), ppc64, ~~and~~ ppc64le. The framework makes sharing code between similar architectures, e.g. arm and arm64, easier by adopting Linux's configured asm symlink. With the asm symlink each architecture gets its own copy of the headers, but then may opt to share the same code.		The kvm-unit-tests framework supports multiple architectures; currently i386, x86_64, armv7 (arm), armv8 (arm64), ppc64, ppc64le, s390x. The framework makes sharing code between similar architectures, e.g. arm and arm64, easier by adopting Linux's configured asm symlink. With the asm symlink each architecture gets its own copy of the headers, but then may opt to share the same code.

	The framework has the following components:		The framework has the following components:

Ajb: http git link has moved on kernel.org

2017-05-15T17:28:15Z

http git link has moved on kernel.org

← Older revision		Revision as of 13:28, 15 May 2017
Line 7:		Line 7:

	The source code can be found on kernel.org's git server:		The source code can be found on kernel.org's git server:
	* [https://git.kernel.org/~~cgit~~/~~virt/kvm/kvm-unit-tests.git https://git.kernel.org/cgit~~/virt/kvm/kvm-unit-tests.git]		* https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
	* git://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git		* git://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
	</noinclude>		</noinclude>

Drjones: /* Contributing */

2017-03-03T13:16:52Z

Contributing

← Older revision		Revision as of 09:16, 3 March 2017
Line 185:		Line 185:
	= Contributing =		= Contributing =

	To contribute new tests ~~and~~ enhancements and fixes to the framework, please submit patches to the KVM mailing list with the additional tag 'kvm-unit-tests' in the subject, i.e. [kvm-unit-tests PATCH]		To contribute new tests or enhancements and fixes to the framework, please submit patches to the KVM mailing list with the additional tag 'kvm-unit-tests' in the subject, i.e. [kvm-unit-tests PATCH]

	[[Category:Docs]][[Category:Testing]][[Category:HowTo]]		[[Category:Docs]][[Category:Testing]][[Category:HowTo]]
	</noinclude>		</noinclude>

Drjones: /* Adding a test */

2017-03-03T13:15:46Z

Adding a test

← Older revision		Revision as of 09:15, 3 March 2017
Line 161:		Line 161:
	1. Create the new unit test's main code file		1. Create the new unit test's main code file
	<pre>		<pre>
	$ cat > ~~arm~~/new-unit-test.c		$ cat > x86/new-unit-test.c
	#include <libcflat.h>		#include <libcflat.h>

Line 171:		Line 171:
	</pre>		</pre>

	2. ~~Add a line like the following to~~ the appropriate ~~config~~/ .~~mak file~~<br>		2. Ensure the appropriate makefile, e.g. x86/Makefile.common, has been updated by adding it to a tests variable<br>
	<pre>		<pre>
	~~$(TEST_DIR)/new-unit~~-~~test.elf: $(cstart.o)~~ $(TEST_DIR)/new-unit-test.o		tests-common = $(TEST_DIR)/new-unit-test.flat
	</pre>		</pre>
	~~And also add <tt>$(TEST_DIR)/new-unit-test.flat</tt> to the tests-common makefile variable.~~ Note, the tests-common variable identifies tests shared between similar architectures, e.g. i386 and x86_64 or arm and arm64. Use the tests makefile variable of a specific architecture's makefile to build the test specifically for that architecture.		Note, the tests-common variable identifies tests shared between similar architectures, e.g. i386 and x86_64 or arm and arm64. Use the tests makefile variable of a specific architecture's makefile to build the test specifically for that architecture.

	3. You can now build and run the test		3. You can now build and run the test
	<pre>		<pre>
	$ make		$ make
	$ ~~arm~~/run ~~arm~~/new-unit-test.flat		$ x86/run x86/new-unit-test.flat
	</pre>		</pre>

Drjones: /* Running tests via Avocado */

2017-03-03T13:06:42Z

Running tests via Avocado

← Older revision		Revision as of 09:06, 3 March 2017
Line 140:		Line 140:
	== Running tests via Avocado ==		== Running tests via Avocado ==

	~~To simplify things one can use~~ [~~https~~:/~~/github.com~~/avocado-framework/~~avocado~~/~~blob~~/~~master/contrib/testsuites/run-kvm-unit-test.sh~~ https://github.com/avocado-framework/avocado/blob/master/contrib/testsuites/run-kvm-unit-test.sh~~] script to run~~ kvm-unit-tests. ~~Simply [http://avocado-framework.readthedocs.io/en/latest/GetStartedGuide.html install Avocado], download~~ the ~~script and use~~ `sh run-kvm-unit-test.sh -h` ~~to see the options~~. By default it downloads the latest kvm-unit-~~test~~ and runs all available tests:		kvm-unit-tests may be run as an [http://avocado-framework.readthedocs.io/en/latest/ Avocado] external testsuite using the [https://github.com/avocado-framework/avocado/blob/master/contrib/testsuites/run-kvm-unit-test.sh Avocado kvm-unit-tests runner script]. Check the available options with `sh run-kvm-unit-test.sh -h`. By default it downloads the latest kvm-unit-tests and runs all available tests.

	<pre>		<pre>
Line 156:		Line 156:
	JOB HTML : /home/medic/avocado/job-results/job-2017-02-23T16.49-216c5cf/html/results.html		JOB HTML : /home/medic/avocado/job-results/job-2017-02-23T16.49-216c5cf/html/results.html
	</pre>		</pre>

	~~The main benefit in using Avocado is to get persistent results along with sysinfo collection and the possibility to re-run the job (or only FAILed cases) or see the difference between two jobs.~~

	= Adding a test =		= Adding a test =