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/lsrc-sigils.t | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 test/lsrc-sigils.t (limited to 'test/lsrc-sigils.t') diff --git a/test/lsrc-sigils.t b/test/lsrc-sigils.t new file mode 100644 index 0000000..98573b2 --- /dev/null +++ b/test/lsrc-sigils.t @@ -0,0 +1,16 @@ + $ . "$TESTDIR/helper.sh" + +Should print @ for links + + $ touch .dotfiles/example + + $ lsrc -F + /*/.example:/*/.dotfiles/example:@ (glob) + +Should print X for files in COPY_ALWAYS + + $ touch .dotfiles/copy + + $ COPY_ALWAYS=copy lsrc -F + /*/.copy:/*/.dotfiles/copy:X (glob) + /*/.example:/*/.dotfiles/example:@ (glob) -- cgit v1.2.3