summaryrefslogtreecommitdiff
path: root/test/README.testsuite
diff options
context:
space:
mode:
Diffstat (limited to 'test/README.testsuite')
-rw-r--r--test/README.testsuite35
1 files changed, 0 insertions, 35 deletions
diff --git a/test/README.testsuite b/test/README.testsuite
deleted file mode 100644
index 0f96b984a9..0000000000
--- a/test/README.testsuite
+++ /dev/null
@@ -1,35 +0,0 @@
-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 sh -c 'DEBUGFAIL="systemd.unit=multi-user.target" make clean setup run'
-
-you can even skip the "clean" and "setup" if you want to run the machine again.
-
-$ sudo sh -c 'DEBUGFAIL="systemd.unit=multi-user.target" make run'