apenwarr-redo/t/passfailtest.do

. ./skip-if-minimal-do.sh

rm -f pleasefail
redo passfail
[ -e passfail ] || exit 42
PF1=$(cat passfail)
touch pleasefail
redo passfail 2>/dev/null && exit 43
[ -e passfail ] || exit 44
PF2=$(cat passfail)
[ "$PF1" = "$PF2" ] || exit 45
rm -f pleasefail
redo passfail || exit 46
PF3=$(cat passfail)
[ "$PF1" != "$PF3" ] || exit 47
Disable the tests that don't work with minimal/do. ...only when running under minimal/do, of course. The tests in question mostly fail because they're testing particular dependency-related behaviour, and minimal/do doesn't support dependencies, so naturally it doesn't work. 2010-12-11 20:54:46 -08:00			`. ./skip-if-minimal-do.sh`

Add a new passfailtest. This tests that the target file isn't removed or changed if building fails. 2010-11-21 06:12:27 -08:00			`rm -f pleasefail`
			`redo passfail`
t/passfailtest.do: just return exit codes, don't print messages. The exit code numbers are useful enough, and the messages are the sort of thing that might turn into lies eventually. 2010-12-06 03:12:02 -08:00			`[ -e passfail ] \|\| exit 42`
Add a new passfailtest. This tests that the target file isn't removed or changed if building fails. 2010-11-21 06:12:27 -08:00			`PF1=$(cat passfail)`
			`touch pleasefail`
t/passfailtest.do: just return exit codes, don't print messages. The exit code numbers are useful enough, and the messages are the sort of thing that might turn into lies eventually. 2010-12-06 03:12:02 -08:00			`redo passfail 2>/dev/null && exit 43`
			`[ -e passfail ] \|\| exit 44`
Add a new passfailtest. This tests that the target file isn't removed or changed if building fails. 2010-11-21 06:12:27 -08:00			`PF2=$(cat passfail)`
t/passfailtest.do: just return exit codes, don't print messages. The exit code numbers are useful enough, and the messages are the sort of thing that might turn into lies eventually. 2010-12-06 03:12:02 -08:00			`[ "$PF1" = "$PF2" ] \|\| exit 45`
Add a new passfailtest. This tests that the target file isn't removed or changed if building fails. 2010-11-21 06:12:27 -08:00			`rm -f pleasefail`
t/passfailtest.do: just return exit codes, don't print messages. The exit code numbers are useful enough, and the messages are the sort of thing that might turn into lies eventually. 2010-12-06 03:12:02 -08:00			`redo passfail \|\| exit 46`
Add a new passfailtest. This tests that the target file isn't removed or changed if building fails. 2010-11-21 06:12:27 -08:00			`PF3=$(cat passfail)`
t/passfailtest.do: just return exit codes, don't print messages. The exit code numbers are useful enough, and the messages are the sort of thing that might turn into lies eventually. 2010-12-06 03:12:02 -08:00			`[ "$PF1" != "$PF3" ] \|\| exit 47`