cram
cram copied to clipboard
Functional tests for command line applications
We're using cram quite successfully for a collection of command line tools concerned with processing geospatial data. In some cases we match numerical data such as XYZ position, the distance...
I would like to be able to write this code: ``` $ command Good morning (optional) Hello. ``` I expect the command being tested to either output `"Good morning\nHello.\n"` or...
Add an option to exit on first failue so `cram --fail-fast ./tests` exits on first failing test case and one can focus only the single test case failing output.
I need to test for a line of command output that starts with "$ ". But this is exactly the pattern that cram uses to run commands in a shell....
hi, I have not given this much thought yet but it would probably be nice to have a simple shell expansion in the test case. For example when tesing a...
Hi, as you can read in the [Debian bug report](https://bugs.debian.org/897516) the test suite fails since some time. COVERAGE=python-coverage PYTHON=python PYTHONPATH=`pwd` scripts/cram \ tests ..s...ss... # Ran 11 tests, 3 skipped,...
Given a file: ``` Simple commands: $ echo foo foo $ printf 'bar\nbaz\n' | cat bar baz Multi-line command: $ foo() { > echo bar > } $ foo bar...