Test for specific exit code
authorKarl Hasselström <kha@treskal.com>
Sun, 6 Jul 2008 16:09:08 +0000 (18:09 +0200)
committerKarl Hasselström <kha@treskal.com>
Tue, 8 Jul 2008 18:35:23 +0000 (20:35 +0200)
commitf03004e2c26efcd6b172a915e8e0d2f9a7cb064b
tree04bf06b4c72cf457099956c086fb1ab3e9009cbf
parentf749e393e47687971777d79c043562a91e4f493d
Test for specific exit code

When a command is supposed to fail in a test, test for the exact error
code we're expecting, not just that it's non-zero. This makes sure
e.g. that a command that's supposed to fail doesn't do so with an
unhandled exception.

Signed-off-by: Karl Hasselström <kha@treskal.com>
24 files changed:
t/README
t/t0001-subdir-branches.sh
t/t0002-status.sh
t/t1000-branch-create.sh
t/t1001-branch-rename.sh
t/t1002-branch-clone.sh
t/t1200-push-modified.sh
t/t1202-push-undo.sh
t/t1203-push-conflict.sh
t/t1205-push-subdir.sh
t/t1301-repair.sh
t/t1302-repair-interop.sh
t/t1400-patch-history.sh
t/t1501-sink.sh
t/t1600-delete-one.sh
t/t1601-delete-many.sh
t/t2000-sync.sh
t/t2101-pull-policy-pull.sh
t/t2200-rebase.sh
t/t2500-clean.sh
t/t2900-rename.sh
t/t3000-dirty-merge.sh
t/t4000-upgrade.sh
t/test-lib.sh