Systemd/test
Zbigniew Jędrzejewski-Szmek fff87a35d9 test: make it easier to override kernel version 2013-04-24 00:25:04 -04:00
..
TEST-01-BASIC test: make it easier to override kernel version 2013-04-24 00:25:04 -04:00
TEST-02-CRYPTSETUP test: make it easier to override kernel version 2013-04-24 00:25:04 -04:00
TEST-03-JOBS test: make it easier to override kernel version 2013-04-24 00:25:04 -04:00
.gitignore update .gitignore 2013-01-28 03:54:49 +01:00
Makefile test: introduce a basic testsuite framework 2012-05-22 16:54:54 +02:00
README.testsuite test: some trivial fixes to test scripts 2013-01-29 19:01:41 -05:00
a.service test: rename test directory 2011-12-31 18:06:56 +01:00
b.service test: rename test directory 2011-12-31 18:06:56 +01:00
c.service test: rename test directory 2011-12-31 18:06:56 +01:00
d.service test: rename test directory 2011-12-31 18:06:56 +01:00
e.service test: rename test directory 2011-12-31 18:06:56 +01:00
end.service test: factor out testsuite.target, end.service 2013-01-25 22:29:56 +01:00
f.service test: rename test directory 2011-12-31 18:06:56 +01:00
g.service test: rename test directory 2011-12-31 18:06:56 +01:00
h.service test: rename test directory 2011-12-31 18:06:56 +01:00
hello-after-sleep.target test: add test for jobs 2013-01-25 22:29:56 +01:00
hello.service test: add test for jobs 2013-01-25 22:29:56 +01:00
rule-syntax-check.py licence: remove references to old FSF address 2012-12-17 11:41:31 +01:00
rules-test.sh udev: test - move test/ and src/test/ 2012-04-14 19:36:47 +02:00
sched_idle_bad.service sched: Only setting CPUSchedulingPriority=rr doesn't work 2012-11-15 16:16:45 +01:00
sched_idle_ok.service sched: Only setting CPUSchedulingPriority=rr doesn't work 2012-11-15 16:16:45 +01:00
sched_rr_bad.service sched: Only setting CPUSchedulingPriority=rr doesn't work 2012-11-15 16:16:45 +01:00
sched_rr_change.service sched: Only setting CPUSchedulingPriority=rr doesn't work 2012-11-15 16:16:45 +01:00
sched_rr_ok.service sched: Only setting CPUSchedulingPriority=rr doesn't work 2012-11-15 16:16:45 +01:00
sleep.service test: add test for jobs 2013-01-25 22:29:56 +01:00
sys.tar.xz udev: test - move test/ and src/test/ 2012-04-14 19:36:47 +02:00
test-functions man: fix a bunch of typos in docs 2012-09-13 19:34:24 +02:00
testsuite.target test: factor out testsuite.target, end.service 2013-01-25 22:29:56 +01:00
udev-test.pl Fix spelling errors using 'codespell' tool 2013-04-15 08:40:05 -04:00
unstoppable.service test: test irreversible jobs 2013-02-23 14:18:17 +01:00

README.testsuite

The extended testsuite only works with uid=0. It contains of several
subdirectories named "test/TEST-??-*", which are run one by one.

To run the extended testsuite do the following:

$ make all
$ cd test
$ sudo make clean check
...
make[1]: Entering directory `/mnt/data/harald/git/systemd/test/TEST-01-BASIC'
Making all in .
Making all in po
Making all in docs/libudev
Making all in docs/gudev
TEST: Basic systemd setup [OK]
make[1]: Leaving directory `/mnt/data/harald/git/systemd/test/TEST-01-BASIC'
...

If one of the tests fails, then $subdir/test.log contains the log file of
the test.

To debug a special testcase of the testsuite do:

$ make all
$ cd test/TEST-01-BASIC
$ sudo make clean setup run

If you want to log in the testsuite virtual machine, you can specify
additional kernel command line parameter with $DEBUGFAIL.

$ sudo make DEBUGFAIL="systemd.unit=multi-user.target" clean setup run

you can even skip the "clean" and "setup" if you want to run the machine again.

$ sudo make DEBUGFAIL="systemd.unit=multi-user.target" run