The problem is, without this line, it won't be easy to match the test error message with the stack trace.

Here's an example output:

```
[error] Test ApplicationTest.simpleCheck failed: expected:<[foo]> but was:<[bar]>
[info] ApplicationTest
[info] x simpleCheck
[error] sbt.ForkMain$ForkError: expected:<[foo]> but was:<[bar]>
[error]     at org.junit.Assert.assertEquals(Assert.java:115)
[error]     at org.junit.Assert.assertEquals(Assert.java:144)
[error]     at ApplicationTest.simpleCheck(ApplicationTest.java:33)
```

That first error message is output by junit-interface when the failure happened.  The second one is output by Play's listener after the test suite finishes.  If you had multiple failures, you'd get this:

```
[error] Test ApplicationTest.simpleCheck failed: expected:<[foo]> but was:<[bar]>
[error] Test ApplicationTest.simpleCheck2 failed: expected:<[foo]> but was:<[bar]>
[info] ApplicationTest
[info] x simpleCheck
[error]     at org.junit.Assert.assertEquals(Assert.java:115)
[error]     at org.junit.Assert.assertEquals(Assert.java:144)
[error]     at ApplicationTest.simpleCheck(ApplicationTest.java:33)
[info] x simpleCheck2
[error]     at org.junit.Assert.assertEquals(Assert.java:115)
[error]     at org.junit.Assert.assertEquals(Assert.java:144)
[error]     at ApplicationTest.simpleCheck(ApplicationTest.java:33)
```

By removing the line, it makes it less clear.  A solution to this could be that we somehow disable that logging from junit-interface, and format the error nicer ourselves.