Related Links
Miscellaneous links of interest related to libvirt
diff --git a/docs/testapi.html.in b/docs/testapi.html.in
new file mode 100644
index 0000000000..9b6161d58c
--- /dev/null
+++ b/docs/testapi.html.in
@@ -0,0 +1,34 @@
+
+
+
+ libvirt-test-API: Python based test suite
+ Libvirt-test-API is a powerful test tool designed to complement
+ existing libvirt test tools such as libvirt-TCK and the internal
+ test suite. It aims at functional regression testing, trying to
+ exercise nearly all the API by the way of the Python bindings.
+ The test API currently covers:
+
+ - domain: all classical lifetime operations, installation of
+ various guests OSes, snapshots
+ - interfaces: define, create, destroy, undefine, NPIV
+ - virtual networks: define, create, destroy, undefine
+ - storage: regression tests for most storage types and configurations
+ dir, disk, netfs, iSCSI, multipath
+
+ Some of the tests need dedicated local resources whose definitions
+ are stored in a configuration file. The tests are defined using
+ Python modules defining the code for the test, this is called
+ a test case, and test configuration files using one
+ or more test case to define a given test scenario.
+ For more details you can look at:
+
+ - A documentation PDF
+ file describing the test suite and how to write test cases
+ and test scenarios.
+
+ Libvirt-test-API is maintained using
+ a GIT
+ repository, and comment, patches and reviews are carried
+ on the libvir-list development list.
+
+
diff --git a/docs/testsuites.html.in b/docs/testsuites.html.in
new file mode 100644
index 0000000000..86fd5eff9b
--- /dev/null
+++ b/docs/testsuites.html.in
@@ -0,0 +1,37 @@
+
+
+
+ Test suites
+ There is a few test suites available to developers for testing
+ a given version of libvirt:
+
+ - the internal test suite: present in the source code, it is run
+ by developers before submitting patches upstream, it is also
+ suggested to have it run and pass as part of the packaging
+ process for distributions. It is run by launching:
+
make check
+ in a source tree after compilation has finished. It doesn't
+ really make functional testing but checks that large portions
+ of the code not interacting directly with virtualization
+ functions properly.
+
+ - the TCK test suite is a functional
+ test suite implemented using the
+ Perl bindings
+ of libvirt. It is available separately as a
+ download, as a
+ package
+ in Fedora distributions, but best is probably to get
+ the version
+ from GIT.
+
- the libvirt-test-API is also a functional
+ test suite, but implemented using the
+ Python bindings
+ of libvirt. It is available separately as a
+ download,
+ or directly get the
+ the version
+ from GIT.
+
+
+
diff --git a/docs/testtck.html.in b/docs/testtck.html.in
new file mode 100644
index 0000000000..c0e700862f
--- /dev/null
+++ b/docs/testtck.html.in
@@ -0,0 +1,39 @@
+
+
+
+ libvirt TCK : Technology Compatibility Kit
+ The libvirt TCK provides a framework for performing testing
+ of the integration between libvirt drivers, the underlying virt
+ hypervisor technology, related operating system services and system
+ configuration. The idea (and name) is motivated by the Java TCK.
+ In particular the libvirt TCK is intended to address the following
+ scenarios:
+
+ - Validate that a new libvirt driver is in compliance
+ with the (possibly undocumented!) driver API semantics
+ - Validate that an update to an existing driver does not
+ change the API semantics in a non-compliant manner
+ - Validate that a new hypervisor release is still providing
+ compatibility with the corresponding libvirt driver usage
+ - Validate that an OS distro deployment consisting of a
+ hypervisor and libvirt release is configured correctly
+
+ Thus the libvirt TCK will allow developers, administrators and users
+ to determine the level of compatibility of their platform, and
+ evaluate whether it will meet their needs, and get awareness of any
+ regressions that may have occurred since a previous test run.
+ For more details you can look at:
+
+ Libvirt-TCK is maintained using
+ a GIT
+ repository, and comment, patches and reviews are carried
+ on the libvir-list development list.
+
+