procps/testsuite
Sami Kerola 00744108c6 docs: add testsuite readme file
Signed-off-by: Sami Kerola <kerolasa@iki.fi>
2012-03-03 18:36:29 +11:00
..
config ps abort causes problems in testsuite 2012-03-03 11:49:48 +11:00
free.test Check for 0 repeat count and tests in free 2012-01-04 10:07:31 +11:00
kill.test Updated testsuite files for new NLS output 2012-01-02 17:39:41 +11:00
lib.test test: add lib/strutils check 2012-03-03 18:36:29 +11:00
pgrep.test Updated testsuite files for new NLS output 2012-01-02 17:39:41 +11:00
pkill.test Updated testsuite files for new NLS output 2012-01-02 17:39:41 +11:00
pmap.test Updated testsuite files for new NLS output 2012-01-02 17:39:41 +11:00
ps.test tests: add SCHED_BATCH test 2012-01-09 21:37:41 +01:00
pwdx.test tests: fix dejagnu pwdx and vmstat checks 2012-02-11 21:42:21 +01: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 fixed uptime check regexp 2012-03-02 23:05:28 +11:00
vmstat.test tests: fix dejagnu pwdx and vmstat checks 2012-02-11 21:42:21 +01:00
w.test fixed uptime check regexp 2012-03-02 23:05:28 +11:00
.gitignore tests: add SCHED_BATCH test 2012-01-09 21:37:41 +01:00
global-conf.exp new free commands 2011-11-23 22:48:49 +11:00
Makefile.am test: add lib/strutils check 2012-03-03 18:36:29 +11:00
README docs: add testsuite readme file 2012-03-03 18:36:29 +11: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.