Run the tests from the top directory:
$ make test $ make test-fsck $ make test-convert
or selectively from the tests/
directory:
$ ./fsck-tests.sh $ ./misc-tests.sh
The verbose output of the tests is logged into a file named after the test category, eg. fsck-tests-results.txt
.
The test are prefixed by a number for ordering and uniquenes. To run a particular test use:
$ make TEST=MASK test
where MASK
is a glob expression that will execute only tests that match the MASK. Here the test number comes handy:
$ make TEST=001\* test-fsck $ TEST=001\* ./fsck-tests.sh
will run the first test in fsck-tests subdirectory.
tests/fsck-tests/:
tests/convert-tests/:
tests/fuzz-tests/:
tests/misc-tests/:
./test.sh
in the test directorytests/common:
tests/test.img:
chmod a+w
for root.It's possible to wrap the tested commands to utilities that might do more checking or catch failures at runtime. This can be done by setting the INSTRUMENT
environment variable:
INSTRUMENT=valgrind ./fuzz-tests.sh # in tests/ make INSTRUMENT=valgrind test-fuzz # in the top directory
The variable is prepended to the command unquoted, all sorts of shell tricks are possible.
Note: instrumentation is not applied to privileged commands (anything that uses the root helper).
Setting the variable TEST_LOG=tty
will print all commands executed by some of the wrappers (run_check
etc), other commands are silent.
Some commands require root privileges (to mount/umount, access loop devices). It is assumed that sudo
will work in some way (no password, password asked and cached). Note that instrumentation is not applied in this case, for safety reasons. You need to modify the test script instead.
The tests are supposed to cleanup after themselves if they pass. In case of failure, the rest of the tests are skipped and intermediate files, mounts and loop devices are kept. This should help to investigate the test failure but at least the mounts and loop devices need to be cleaned before the next run.
This is partially done by the script clean-tests.sh
, you may want to check the loop devices as they are managed on a per-test basis.
misc-tests
if not sure. For an easy start copy an existing test.sh
script from some test that might be close to the purpose of your new test.Use the highest unused number in the sequence, write a short descriptive title and join by dashes -
.
Write a short description of the bug and how it's teste to the comment at the begining of test.sh
.
Write the test commands, comment anything that's not obvious.
Test your test. Use the TEST
variable to jump right to your test:
$ make TEST=012\* tests-misc # from top directory $ TEST=012\* ./misc-tests.sh # from tests/
btrfs-progs: tests: add 012-subvolume-sync-must-wait