suggestion for deployment

[GoogleCodeExporter]

Hello,
This is not a bug report, but rather a suggestion or feature request.

Suppose shunit2 were made executable, and suppose its Makefile had an
"install" target which installed it to /usr/local/bin.

Then, it could be invoked from the test script without needing to hard-code
the path:

  . $(which shunit2)

Granted the only reason it would be made executable is so that the "which"
program could find it.  However, if you run it as an executable it simply
reports that no tests were run, which can be considered graceful degradation.

And/or, it could be improved to accept a test-script via the command line,
so you could invoke it like:

  shunit2 my-tests

This change would make it easier to deploy tests that depend on shunit2
without bundling shunit2 with the application.

Original issue reported on code.google.com by jjfoe...@earthlink.net on 17 Dec 2008 at 6:14

[GoogleCodeExporter]

Interesting... Let me see how difficult this will be.

Original comment by kate.war...@gtempaccount.com on 27 Dec 2008 at 1:04

[GoogleCodeExporter]

This will be supported in the 2.1.6 release, and the code for this is now 
checked into the HEAD of the code base.

Original comment by kate.war...@gtempaccount.com on 3 May 2010 at 10:34

• Changed state: Fixed

[GoogleCodeExporter]

I can't find the make file, not in the latest release nor in the HEAD of the 
code base?

Original comment by p...@born2code.net on 28 May 2013 at 10:00