procps/testsuite
Craig Small 647a2aa9e1 testsuite: Test for uptime --pretty
References:
 procps-ng/procps#263
2023-01-16 17:22:26 +11:00
..
config testsuite: Update the library tests for new location 2022-08-29 20:40:45 +10:00
free.test build-sys: Update tests to new binary locations 2022-08-29 19:13:10 +10:00
kill.test build-sys: Update tests to new binary locations 2022-08-29 19:13:10 +10:00
lib.test testsuite: Update the library tests for new location 2022-08-29 20:40:45 +10:00
pgrep.test pgrep: Support matching on the presence of a userspace signal handler 2023-01-15 04:05:40 +00:00
pkill.test build-sys: Update tests to new binary locations 2022-08-29 19:13:10 +10:00
pmap.test build-sys: Update tests to new binary locations 2022-08-29 19:13:10 +10:00
ps.test ps: Correct BSD c option 2022-12-19 16:50:12 +11:00
pwait.test pgrep: Support matching on the presence of a userspace signal handler 2023-01-15 04:05:40 +00:00
pwdx.test build-sys: Update tests to new binary locations 2022-08-29 19:13:10 +10:00
skill.test skill: Restore the -p flag functionality 2022-12-12 16:46:36 +11:00
slabtop.test build-sys: Update tests to new binary locations 2022-08-29 19:13:10 +10:00
sysctl.test build-sys: Update tests to new binary locations 2022-08-29 19:13:10 +10:00
uptime.test testsuite: Test for uptime --pretty 2023-01-16 17:22:26 +11:00
vmstat.test build-sys: Update tests to new binary locations 2022-08-29 19:13:10 +10:00
w.test w: add --pids option to display the pid of the login and best processes. 2023-01-15 04:15:32 +00:00
.gitignore tests: add SCHED_BATCH test 2012-01-09 21:37:41 +01:00
Makefile.am
README
sysctl_glob_test.conf sysctl: Support systemd glob patterns 2021-09-15 20:07:32 +10:00
sysctl_slash_test.conf sysctl: print dotted keys again 2022-04-09 14:18:28 +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.