assert.sh is test-driven development in the Bourne again shell.
. assert.sh # `echo test` is expected to write "test" on stdout assert "echo test" "test" # `seq 3` is expected to print "1", "2" and "3" on different lines assert "seq 3" "1\n2\n3" # exit code of `true` is expected to be 0 assert_raises "true" # exit code of `false` is expected to be 1 assert_raises "false" 1 # end of test suite assert_end examples
If you had written the above snippet into
tests.sh you could invoke it
without any extra hassle:
$ ./tests.sh all 4 examples tests passed in 0.014s.
Watch out to have
tests.sh executable (
chmod +x tests.sh), otherwise
you need to invoke it with
Now, we will add a failing test case to our suite:
# expect `exit 127` to terminate with code 128 assert_raises "exit 127" 128
Remember to insert test cases before
assert_end (or write another
assert_end to the end of your file). Otherwise test statistics will be
When run, the output is:
test #5 "exit 127" failed: program terminated with code 127 instead of 128 1 of 5 examples tests failed in 0.019s.
- lightweight interface:
- minimal setup -- source
assert.shand you're done
- test grouping in individual suites
- time benchmarks with real-time display of test progress
- run all tests, stop on first failure, or collect numbers only
You wrote an application. Following sane development practices, you want to
protect yourself against introducing errors with a test suite. Even though most
languages have excellent testing tools, modifying process state (input
command line arguments
argv, environment variables) is awkard in most
languages. The shell was made to do just that, so why don't run the tests in
assert <command> [stdout] [stdin]
Check for an expected output when running your command. stdout supports all control sequences printf(1) interprets, eg.
\nfor a newline. The default stdout is assumed to be empty.
assert_raises <command> [exitcode] [stdin]
Verify command terminated with the expected status code. The default exitcode is assumed to be 0.
Finalize a test suite and print statistics.
Command line options
assert.sh --help for command line options on test runners.
-v, --verbose Generate real-time output for every individual test run. -x, --stop Stop running tests after the first failure. (Default: run all tests.) -i, --invariant Do not measure runtime for suites. Useful mainly to parse test output. -d, --discover Collect test suites and number of tests only; don't run any tests. -h Show brief usage information and exit. --help Show usage manual and exit.
- Fixed Mac OS compatibility (closes #3).
- Added support for
set -uenvironments (closes #1).
- Fixed several leaks of stderr.
- Fixed propagation of options to nested test suites.
- Added support for
- ShUnit is a testing framework of the xUnit family for Bourne derived shells. It is quite feature-rich but requires a whole lot of boilerplate to write a basic test suite. assert.sh aims to be lightweight and easy to setup.
- shUnit2 is a modern xUnit-style testing framework. It comes with a bunch of magic to remove unneccessary verbosity. It requires extra care when crafting test cases with many subprocess invocations as you have to fall back to shell features to fetch results. assert.sh wraps this functionality out of the box.
- A Test Anything Protocol (TAP) producer with an inherently natural-language-
style API. Unfortunately it's only of draft quality and decouples the test
runner from analysis, which does not allow for assert.sh features such as