The shelltestrunner package

[Tags: gpl, program]

Run a given program through "shell" tests specifed by one or more test files, each of which specifies: command-line arguments, input, expected output, expected stderr output, and expected exit code. This was extracted from the hledger project, and inspired by the tests in John Wiegley's ledger project. This uses test-framework's test runner. Any command-line options are passed through to the test-framework runner, but they must not contain spaces, so use eg -tpattern not -t pattern. You may be able to get a big speedup by running tests in parallel: try -j8. Usage: $ shelltestrunner [testrunneropts] executable testfile1 [testfile2 ...] Test file format: ; 0 or more comment lines beginning with ; -opt1 -opt2 arg1 arg2 <<< 0 or more lines of input >>> 0 or more lines of expected output >>>2 0 or more lines of expected error output >>>= expected numeric exit code Initial lines beginning with ; are ignored. The next line is the command-line arguments which will be appended to the executable name. All remaining fields are optional; when omitted they are assumed to be "", "", "", and 0 respectively. Issues: - on mac, will hang if executable does not read stdin - output order is mixed up - can't test input/ouput which does not end with newline


Versions0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1.0, 1.1, 1.2, 1.2.1, 1.3, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5
Change logNone available
Dependenciesbase (>=3 && <5), HUnit, parseargs (==0.1.*), parsec, process, test-framework, test-framework-hunit (==0.2.*) [details]
AuthorSimon Michael <>
MaintainerSimon Michael <>
Home page
UploadedSat Jul 11 22:38:28 UTC 2009 by SimonMichael
DistributionsDebian:1.3.5, LTSHaskell:1.3.5, NixOS:1.3.5, Stackage:1.3.5
Downloads3886 total (95 in last 30 days)
0 []
StatusDocs not available [build log]
All reported builds failed as of 2015-11-24 [all 5 reports]


Maintainers' corner

For package maintainers and hackage trustees