etorreborre/specs2 — Issue #55: Use exit codes to signify test failure in specs2.run
Author: djspiewak
Created: 2012-02-08 03:55:35+00:00
State: open

The command line runner, `specs2.run`, provides no programmatic feedback to its parent process indicating success or failure of the specification in question. It should produce an exit value of 0 for a successful test and something non-zero for a failed test (preferably 1 for failed test and 100 for error, or something distinct like that). This is actually a critical issue for me, since I need to be able to run a Specs2 specification as a forked sub-process under SBT, reporting the results back as an error in the build on failure.