procps/testsuite
2022-08-29 19:13:10 +10:00
..
config build-sys: Update tests to new binary locations 2022-08-29 19:13:10 +10:00
free.test build-sys: Update tests to new binary locations 2022-08-29 19:13:10 +10:00
kill.test build-sys: Update tests to new binary locations 2022-08-29 19:13:10 +10:00
lib.test tests: Fix paths for testsuite 2021-02-24 20:41:38 +11:00
pgrep.test build-sys: Update tests to new binary locations 2022-08-29 19:13:10 +10:00
pkill.test build-sys: Update tests to new binary locations 2022-08-29 19:13:10 +10:00
pmap.test build-sys: Update tests to new binary locations 2022-08-29 19:13:10 +10:00
ps.test build-sys: Update tests to new binary locations 2022-08-29 19:13:10 +10:00
pwait.test build-sys: Update tests to new binary locations 2022-08-29 19:13:10 +10:00
pwdx.test build-sys: Update tests to new binary locations 2022-08-29 19:13:10 +10:00
slabtop.test build-sys: Update tests to new binary locations 2022-08-29 19:13:10 +10:00
sysctl.test build-sys: Update tests to new binary locations 2022-08-29 19:13:10 +10:00
uptime.test build-sys: Update tests to new binary locations 2022-08-29 19:13:10 +10:00
vmstat.test build-sys: Update tests to new binary locations 2022-08-29 19:13:10 +10:00
w.test build-sys: Update tests to new binary locations 2022-08-29 19:13:10 +10:00
.gitignore tests: add SCHED_BATCH test 2012-01-09 21:37:41 +01:00
Makefile.am slabtop: Check for bad d and o option combination 2021-03-11 22:10:37 +11:00
README docs: add testsuite readme file 2012-03-03 18:36:29 +11:00
sysctl_glob_test.conf sysctl: Support systemd glob patterns 2021-09-15 20:07:32 +10:00
sysctl_slash_test.conf sysctl: print dotted keys again 2022-04-09 14:18:28 +10:00

How to use check suite
----------------------

You need DejaGNU package.  Assuming you have it all you need to do is

make check


Something failed now what
-------------------------

First determine what did not work.  If only one check failed you can
run it individually in debugging mode.  For example

runtest -a -de -v w.test/w.exp
Expect binary is /usr/bin/expect
Using /usr/share/dejagnu/runtest.exp as main test driver
[...]

Do not bother capturing screen output, it is in testrun.log which
test suite generated.

$ ls  testrun.* dbg.log
dbg.log  testrun.log  testrun.sum

The reason why test failed should be in dbg.log.  Assuming you
figured out the reason you could write a patch fixing w.test/w.exp
and send it to upstream.

If you do not know how, or have time, to fix the issue create tar.gz
file containing test run logs and submit it to upstream maintainers.
Notice that in later case upstream sometimes has to ask clarifying
questions about environment where problem occurred.