procps/testsuite
Pierre Labastie 1b63eb8671 Improved regexp test for pmap
The change in pmap is necessary if it happens that the whole output of
pmap -X or -XX has been done before the second regexp is matched. Since
the matching is greedy, it is matched by the full output, so that
nothing is left for the third regexp and the test fails with
FAIL: extra extended output (footer).

Reference: http://comments.gmane.org/gmane.linux.lfs.devel/13961

Signed-off-by: Craig Small <csmall@enc.com.au>
2013-04-07 18:31:26 +10:00
..
config Revert "Fixed last_value for loops over 99999" 2013-04-07 08:30:48 +10:00
free.test all: fix misspellings in docs and program comments 2012-04-25 13:46:02 +10:00
kill.test
lib.test lib: add fileutils file with stream error checking facility 2012-03-23 15:57:41 +01:00
pgrep.test Debian Bug report #526355 2012-08-29 16:47:51 +10:00
pkill.test Run pgrep and pkill tests whithout host ps 2012-06-28 21:53:22 +10:00
pmap.test Improved regexp test for pmap 2013-04-07 18:31:26 +10: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
sysctl.test
uptime.test test for previous commit 2012-12-26 23:21:44 +11:00
vmstat.test tests: fix dejagnu pwdx and vmstat checks 2012-02-11 21:42:21 +01:00
w.test Fix w tests when no user is logged in 2012-05-08 22:51:19 +10:00
.gitignore
global-conf.exp
Makefile.am Conditionally test kill when we compile it 2013-03-25 21:46:17 +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.