X-Git-Url: http://git.annexia.org/?p=libguestfs.git;a=blobdiff_plain;f=HACKING;h=1121deb362f2a3b3f4fa0f32be202724c1a12f27;hp=9ae20a6f055feba0db22f60138ab990347f7aeaa;hb=4c5038ab54fb6fdff75ca8d5fdda9e73f48a5050;hpb=04d8209077d2227eb1d42695ba71147f78987050 diff --git a/HACKING b/HACKING index 9ae20a6..1121deb 100644 --- a/HACKING +++ b/HACKING @@ -69,7 +69,11 @@ appliance/ The qemu appliance, build scripts and so on. capitests/ - Automated tests of the C API. + Automated tests of the C API. See "Tests" below. + +cat/ + The 'virt-cat', 'virt-filesystems' and 'virt-ls' commands and + documentation. contrib/ Outside contributions, experimental parts. @@ -80,6 +84,9 @@ csharp/ daemon/ The daemon that runs inside the guest and carries out actions. +df/ + 'virt-df' command and documentation. + examples/ The examples. @@ -120,6 +127,9 @@ m4/ ocaml/ OCaml bindings. +php/ + PHP bindings. + po/ Translations of simple gettext strings. For translations of longer documents, see po-docs/. @@ -138,14 +148,14 @@ python/ regressions/ Regression tests. +rescue/ + 'virt-rescue' command and documentation. + ruby/ Ruby bindings. tools/ - Command line tools like virt-cat, virt-df, virt-edit and more. - In versions <= 1.0.73 these were all in separate directories - like cat/, df/, edit/, but since then we moved them all into - one directory to simplify builds. + Command line tools written in Perl (virt-resize and more). src/ Source code to the C library. @@ -153,6 +163,48 @@ src/ test-tool/ Interactive qemu/kernel test tool. +Tests +---------------------------------------------------------------------- + +You can supply zero or as many tests as you want per API call. + +The test environment has 4 block devices: + /dev/sda 500MB General block device for testing. + /dev/sdb 50MB /dev/sdb1 is an ext2 filesystem used for testing + filesystem write operations. + /dev/sdc 10MB Used in a few tests where 2 block devices are needed. + /dev/sdd - ISO with fixed content (see images/test.iso). + +To be able to run the tests in a reasonable amount of time, the +virtual machine and block devices are reused between tests. So don't +try testing kill_subprocess :-x Between each test we blockdev-setrw, +umount-all, lvm-remove-all. + +Each test starts with an initial scenario, selected using one of the +'Init*' expressions, described in generator/generator_types.ml. These +initialize the disks in a particular way as described. You should not +assume anything about the previous contents of other disks that are +not initialized. + +You can add a prerequisite clause to any individual test. This is a +run-time check, which, if it fails, causes the test to be skipped. +Useful if testing a command which might not work on all variations of +libguestfs builds. A test that has prerequisite of 'Always' is run +unconditionally. + +In addition, packagers can skip individual tests by setting the +environment variables: eg: + + SKIP_TEST__=1 SKIP_TEST_COMMAND_3=1 (skips test #3 of command) + SKIP_TEST_=1 SKIP_TEST_ZEROFREE=1 (skips all zerofree tests) + +and packagers can run only certain tests by setting eg: + + TEST_ONLY="vfs_type zerofree" + +See capitests/tests.c for more details of how these environment +variables work. + Debugging ----------------------------------------------------------------------