test/README.testsuite: add documentation for the testsuite

1 files changed, 35 insertions, 0 deletions

diff --git a/test/README.testsuite b/test/README.testsuite
new file mode 100644
index 0000000000..0f96b984a9
--- /dev/null
+++ b/test/README.testsuite
@@ -0,0 +1,35 @@
+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'