ddcb1e4e92
The unit tests are tiny guest operating systems that generally execute only tens of lines of C and assembler test code in order to obtain its PASS/FAIL result. Unit tests provide KVM and virt hardware functional testing by targeting the features through minimal implementations of their use per the hardware specification. The simplicity of unit tests make them easy to verify they are correct, easy to maintain, and easy to use in timing measurements. Unit tests are also often used for quick and dirty bug reproducers. The reproducers may then be kept as regression tests. It's strongly encouraged that patches implementing new KVM features are submitted with accompanying unit tests. Signed-off-by: Cyril Bur <cyrilbur@gmail.com> [Thomas: - order architecture dependencies in Config.in alphabetically. - rewrap Config.in help text, lines were too long - add an empty line between the package description and the upstream project URL in the Config.in help text - don't make KVM_UNIT_TESTS_ARCH default to $(ARCH). This was not correct for i386 for example. Instead, just handle the few architectures that the package supports. - remove useless double quotes in variable definitions. - remove --prefix="$(TARGET_DIR)" from CONF_OPTS. It was installing everything in /share/ and not /usr/share/, and setting the prefix to TARGET_DIR at configure time is not good. Instead, pass DESTDIR at installation time.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
22 lines
1.0 KiB
Plaintext
22 lines
1.0 KiB
Plaintext
config BR2_PACKAGE_KVM_UNIT_TESTS
|
|
bool "kvm-unit-tests"
|
|
depends on BR2_arm || BR2_i386 || BR2_powerpc64 || \
|
|
BR2_powerpc64le || BR2_x86_64
|
|
help
|
|
kvm-unit-tests is a project as old as KVM. As its name
|
|
suggests, it's purpose is to provide unit tests for KVM. The
|
|
unit tests are tiny guest operating systems that generally
|
|
execute only tens of lines of C and assembler test code in
|
|
order to obtain its PASS/FAIL result. Unit tests provide KVM
|
|
and virt hardware functional testing by targeting the
|
|
features through minimal implementations of their use per
|
|
the hardware specification. The simplicity of unit tests
|
|
make them easy to verify they are correct, easy to maintain,
|
|
and easy to use in timing measurements. Unit tests are also
|
|
often used for quick and dirty bug reproducers. The
|
|
reproducers may then be kept as regression tests. It's
|
|
strongly encouraged that patches implementing new KVM
|
|
features are submitted with accompanying unit tests.
|
|
|
|
http://www.linux-kvm.org/page/KVM-unit-tests
|