procps/testsuite
Craig Small 4706f225c9 testsuite: Add sysctl test for directory checks
Adds a test to try to write a sysctl parameter above /proc
and passes if it gives an error message.

References:
 commit f25d462166
2021-09-15 20:16:06 +10:00
..
config sysctl: Support systemd glob patterns 2021-09-15 20:07:32 +10:00
free.test testsuite: Add test for free committed 2021-06-16 20:34:33 +10:00
kill.test kill: use sigqueue to pass value with the signal. 2020-05-11 17:36:12 +10:00
lib.test tests: Fix paths for testsuite 2021-02-24 20:41:38 +11:00
pgrep.test testsuite: pgrep: Provide test for matching a more than 4k command line; beware as TCL does not seem to match on strings >4k 2019-09-21 17:00:53 +10:00
pkill.test build-sys: Enable testing of sigqueue 2020-05-11 16:59:18 +10:00
pmap.test
ps.test misc: fix ps etime tests 2018-05-03 21:13:16 +10:00
pwait.test build-sys: Make pwait test dependent on pwait built 2020-12-22 15:20:30 +11:00
pwdx.test
slabtop.test slabtop: Check for bad d and o option combination 2021-03-11 22:10:37 +11:00
sysctl.test testsuite: Add sysctl test for directory checks 2021-09-15 20:16:06 +10:00
uptime.test
vmstat.test build-sys: Handle zero length diskstats in tests 2021-03-29 22:23:03 +11:00
w.test
.gitignore
Makefile.am slabtop: Check for bad d and o option combination 2021-03-11 22:10:37 +11:00
README
sysctl_glob_test.conf sysctl: Support systemd glob patterns 2021-09-15 20:07:32 +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.