playframework/playframework — pull request #1841 by richdougherty (2013-10-22 22:22:10+00:00)
Title: [2.2] Test results don't propagate to runner

The behaviour of the sbt `test` command has changing between Play 2.1.5 and Play 2.2. In 2.1.5 if a test failed then the command would fail. In 2.2 it passes regardless of whether the tests have passed or failed.

Simple test case:

- Download play2.2
- Create new play project
- Modify any line in tests/ApplicationSpec.scala to make a test fail
- Run the test and observe that although the test clearly fails, the sbt task is successful (in fact the test summary is not populated)

For example, this is the output I get after changing the expected mime type to something else:
```
[info] Compiling 1 Scala source to /home/shildrew/Downloads/test2.2/target/scala-2.10/test-classes...
[info] IntegrationSpec
[info] Application should
[info] + work from within a browser
[info] Total for specification IntegrationSpec
[info] Finished in 2 seconds, 410 ms
[info] 1 example, 0 failure, 0 error
[info] ApplicationSpec
[info] Application should
[info] + send 404 on a bad request
[info] x render the index page
[error] 'Some(text/html)' is Some but text/html does not satisfy the given predicate (ApplicationSpec.scala:26)
[info] Total for specification ApplicationSpec
[info] Finished in 119 ms
[info] 2 examples, 1 failure, 0 error
[info] Passed: Total 0, Failed 0, Errors 0, Passed 0
[success] Total time: 7 s, completed 16-Oct-2013 16:31:32
```