procps/testsuite/pwdx.test/pwdx.exp


make_testproc

set pwdx "${topdir}src/pwdx"
# Run pwdx with no arguments
set test "pwdx no args"
spawn $pwdx
expect_pass "$test" "^\\s*Usage:\\s+\(lt-\)\?pwdx \\\[options\\\] pid\.\.\."

# Run pwdx with pid 0 which is invalid
set test "pwdx pid 0 should be invalid"
spawn $pwdx 0
expect_pass "$test" "\(lt-\)\?pwdx\: invalid process id\: 0"

# Run pwdx with existing pid
set test "pwdx find test process cwd"
set my_pwd [ pwd ]
spawn $pwdx $testproc1_pid
expect_pass "$test" "^$testproc1_pid: $my_pwd"

# Cleanup
kill_testproc
testsuite fixes 2011-11-23 16:14:51 +05:30
Create test process For the test suite, procps used to use sleep which would just create a process or two to test the tools against. Some setups coreutils creates all programs including sleep into one blob which means a lot of the tests fail, see issue #2 procps has its own sleep program now. 2015-06-13 10:34:31 +05:30			`make_testproc`

build-sys: Update tests to new binary locations 2022-08-29 14:43:10 +05:30			`set pwdx "${topdir}src/pwdx"`
testsuite fixes 2011-11-23 16:14:51 +05:30			`# Run pwdx with no arguments`
			`set test "pwdx no args"`
More testing added for procps 2011-11-30 17:41:35 +05:30			`spawn $pwdx`
Updated testsuite files for new NLS output 2012-01-02 12:09:41 +05:30			`expect_pass "$test" "^\\s*Usage:\\s+\(lt-\)\?pwdx \\\[options\\\] pid\.\.\."`
testsuite fixes 2011-11-23 16:14:51 +05:30
Fixing tests due to some results Makefile will now only test for Linux systems, a work around in the makefile due to some silly redefine restrictions. uptime and w now won't error due to being one user logged in, thanks to Sami for the patch kill processes by pid test commented out due to false negatives pwdx process 1 check also commented out due to false negatives 2011-12-03 19:20:36 +05:30			`# Run pwdx with pid 0 which is invalid`
			`set test "pwdx pid 0 should be invalid"`
			`spawn $pwdx 0`
tests: fix dejagnu pwdx and vmstat checks The pwdx check expected error message, which where in use for only short period of time. The old message was put in place in commit 9d47cb0c38137581a46951fb7c6fa2a1dc8c24cf The vmstat issue was triggered by 'sr0' cdrom device, which gives following unexpected output. Fix simply ignores partitions which has zero activity. Besides such partitions probably would not apply as good candidate of -p option anyway. $ vmstat -p sr0 Partition was not found Reported-By: Moritz Muehlenhoff <jmm@debian.org> Bug-Debian: http://bugs.debian.org/656508 Signed-off-by: Sami Kerola <kerolasa@iki.fi> 2012-02-10 01:48:14 +05:30			`expect_pass "$test" "\(lt-\)\?pwdx\: invalid process id\: 0"`
testsuite fixes 2011-11-23 16:14:51 +05:30
			`# Run pwdx with existing pid`
Create test process For the test suite, procps used to use sleep which would just create a process or two to test the tools against. Some setups coreutils creates all programs including sleep into one blob which means a lot of the tests fail, see issue #2 procps has its own sleep program now. 2015-06-13 10:34:31 +05:30			`set test "pwdx find test process cwd"`
			`set my_pwd [ pwd ]`
			`spawn $pwdx $testproc1_pid`
			`expect_pass "$test" "^$testproc1_pid: $my_pwd"`
testsuite fixes 2011-11-23 16:14:51 +05:30
Create test process For the test suite, procps used to use sleep which would just create a process or two to test the tools against. Some setups coreutils creates all programs including sleep into one blob which means a lot of the tests fail, see issue #2 procps has its own sleep program now. 2015-06-13 10:34:31 +05:30			`# Cleanup`
			`kill_testproc`