procps/testsuite
Craig Small 5d8746b941 misc: fix ps etime tests
The test assumes only one process appears which, depending on the
speed of things, may not be true. It now matches one to many process
lines.
2018-05-03 21:13:16 +10:00
..
config Do not link test process to libprocps 2015-06-14 08:54:59 +10:00
free.test free: Update tests and fix for previous patch 2018-01-13 16:12:19 +11:00
kill.test kill: -l space between name parses correctly 2017-05-22 22:15:59 +10:00
lib.test lib: add fileutils file with stream error checking facility 2012-03-23 15:57:41 +01:00
pgrep.test pgrep: warning about 15+ chars name only if zero matches found 2017-01-26 16:52:23 +11:00
pkill.test testsuite: check for trailing garbage in pkill 2015-10-14 21:31:56 +11:00
pmap.test Update help files 2014-02-02 18:13:01 +11:00
ps.test misc: fix ps etime tests 2018-05-03 21:13:16 +10:00
pwdx.test Create test process 2015-06-13 15:04:31 +10:00
slabtop.test Updated testsuite files for new NLS output 2012-01-02 17:39:41 +11:00
sysctl.test Updated testsuite files for new NLS output 2012-01-02 17:39:41 +11:00
uptime.test test for previous commit 2012-12-26 23:21:44 +11:00
vmstat.test Skip tests where /proc/vmstat unreadable 2015-06-13 15:13:39 +10:00
w.test Fix w tests when no user is logged in 2012-05-08 22:51:19 +10:00
.gitignore tests: add SCHED_BATCH test 2012-01-09 21:37:41 +01:00
Makefile.am Port of merge request 49 to newlib 2017-08-19 23:05:22 +10:00
README docs: add testsuite readme file 2012-03-03 18:36:29 +11:00

README

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.