procps/testsuite
Craig Small f4cc9720ee Reduced partition type check
vmstat -p checks used to fail on systems with odd
partition tables, including some Debian buildd servers.
This change limits what sort of test partitions are used,
otherwise the test is skipped.

There probably are other valid partitions, these can be added
later, if known.
2014-05-27 20:49:16 +10:00
..
config procps-ng : tests, remove which dependency 2013-05-26 07:30:16 +10:00
free.test all: fix misspellings in docs and program comments 2012-04-25 13:46:02 +10:00
kill.test skip kill test too if running runtest 2013-05-26 07:25:55 +10:00
lib.test lib: add fileutils file with stream error checking facility 2012-03-23 15:57:41 +01:00
pgrep.test Skip some tests if kill cannot be found 2013-10-09 19:18:55 +11:00
pkill.test Skip some tests if kill cannot be found 2013-10-09 19:18:55 +11: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 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 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 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 procps-ng testsuite : simplify DEJAGNU workaround 2013-05-26 07:32:02 +10: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.