summaryrefslogtreecommitdiff
path: root/testprogs/blackbox/subunit.sh
AgeCommit message (Collapse)AuthorFilesLines
2013-03-04subunit: Add a sh macro for skipping a testAndrew Bartlett1-0/+10
Reviewed-by: Stefan Metzmacher <metze@samba.org>
2011-02-16testprogs/blackbox/subunit: add testok() for easier integration of s3 tests.Michael Adam1-0/+9
2011-02-07blackbox: removed assumption of build directoryAndrew Tridgell1-0/+8
this fixes the blackbox tests for a top level build Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org>
2010-07-10testprogs/blackbox/subunit.sh: initialize failed to 0Stefan Metzmacher1-0/+3
This is a short-term workarround for broken scripts, which use "exit $failed", without initializing failed. We need a discussion on the mailing list how to handle this in a nicer way. This should fix some random failures in the blackbox tests. metze
2009-09-10testprogs:subunit.sh: Add function for expected failures.Andrew Kroeger1-0/+15
The testit_expect_failure() function is like the testit() function, with reversed error detection logic. This reversal only affects the pass/fail logic and logging - the original return code from the command is still returned to the calling script.
2009-01-08s4:blackbox: don't remove newlines in the subunit failure outputStefan Metzmacher1-1/+1
metze
2008-05-21subunit.sh: Properly capture and pass on the command output.Andrew Kroeger1-2/+2
Previously, the output from $cmdline was never captured. In case of a failure, there was no output being passed to the subunit_fail_test() function, but that function contains a call to "cat -". This caused the script to hang indefinitely waiting for input. We now capture $cmdline output (including mapping stderr to stdout) using backticks, and then pipe that output to the subunit_fail_test() if there is a failure. (This used to be commit c0234d13192c1871971b45121249395ef15c5ae5)
2008-04-16Use library for subunit test functions.Jelmer Vernooij1-0/+67
(This used to be commit 690924dc7f43b69b9c4cfc1dd0c9c6e83d333518)