procps/testsuite
Craig Small 12f13f9fc2 Update free testsuite
free got a makeover to suit the newer kernel memory management.
This commit updates the tests to follow the new output for free

Signed-off-by: Craig Small <csmall@enc.com.au>
2014-08-19 22:43:33 +10:00
..
config Reliably kill test processes 2014-07-01 18:51:21 +10:00
free.test Update free testsuite 2014-08-19 22:43:33 +10:00
kill.test skip kill test too if running runtest 2013-05-26 07:25:55 +10:00
lib.test
pgrep.test Reliably kill test processes 2014-07-01 18:51:21 +10:00
pkill.test Reliably kill test processes 2014-07-01 18:51:21 +10:00
pmap.test Update help files 2014-02-02 18:13:01 +11:00
ps.test ps.test: see truncated user/group names as valid 2012-12-13 21:45:28 +11:00
pwdx.test
slabtop.test
sysctl.test
uptime.test test for previous commit 2012-12-26 23:21:44 +11:00
vmstat.test Reduced partition type check 2014-05-27 20:49:16 +10:00
w.test
.gitignore
Makefile.am procps-ng testsuite : simplify DEJAGNU workaround 2013-05-26 07:32:02 +10: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.