From a5344a3940f292d8d4f8907f92a54bf726b87e44 Mon Sep 17 00:00:00 2001 From: patrick brisbin Date: Fri, 23 Aug 2013 14:31:32 -0400 Subject: An integration test suite This test suite uses cram to run integration tests through `/bin/sh`. The tests are all high-level acceptance tests; they should work regardless of the implemention code. To run them, you must first install cram: sudo pip install cram Then the `check` target will run them: make check Failure output should be printed clearly to stdout, but in general: full test output is in `test/test-suite.log` and output specific to a test named `foo.t` is in `foo.t.log`. Tests are now encouraged in `CONTRIBUTING.md` as part of the normal pull request process. This is a TAP-enabled test suite. --- test/mkrc-usage.t | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 test/mkrc-usage.t (limited to 'test/mkrc-usage.t') diff --git a/test/mkrc-usage.t b/test/mkrc-usage.t new file mode 100644 index 0000000..c9ede8d --- /dev/null +++ b/test/mkrc-usage.t @@ -0,0 +1,14 @@ + $ . "$TESTDIR/helper.sh" + +no arguments should output usage information and exit 1 + + $ mkrc + Usage: mkrc [-hvqo] [-t TAG] [-d DIR] FILES ... + see mkrc(1) and rcm(5) for more details + [1] + +-h should output usage information and exit 0 + + $ mkrc -h + Usage: mkrc [-hvqo] [-t TAG] [-d DIR] FILES ... + see mkrc(1) and rcm(5) for more details -- cgit v1.2.3