5 <p>There is a few test suites available to developers for testing
6 a given version of libvirt:
</p>
8 <li>the internal test suite: present in the source code, it is run
9 by developers before submitting patches upstream, it is also
10 suggested to have it run and pass as part of the packaging
11 process for distributions. It is run by launching:
13 in a source tree after compilation has finished. It doesn't
14 really make functional testing but checks that large portions
15 of the code not interacting directly with virtualization
18 <li>the
<a href=
"testtck.html">TCK test suite
</a> is a functional
19 test suite implemented using the
20 <a href=
"http://search.cpan.org/dist/Sys-Virt/">Perl bindings
</a>
21 of libvirt. It is available separately as a
22 <a href=
"ftp://libvirt.org/libvirt/tck/">download
</a>, as a
23 <a href=
"http://rpmfind.net/linux/rpm2html/search.php?query=libvirt-tck">package
</a>
24 in Fedora distributions, but best is probably to get
25 the
<a href=
"http://libvirt.org/git/?p=libvirt-tck.git">version
27 <li>the
<a href=
"testapi.html">libvirt-test-API
</a> is also a functional
28 test suite, but implemented using the
29 <a href=
"python.html">Python bindings
</a>
30 of libvirt. It is available separately as a
31 <a href=
"ftp://libvirt.org/libvirt/libvirt-test-API/">download
</a>,
33 the
<a href=
"http://libvirt.org/git/?p=libvirt-test-API.git">version