I demoed ccat at GopherCon 2015. Enjoy :-)
This happens mainly because we are running JUnit 3 tests with the JUnit 4 runner. Before version 4.6, the JUnit 4 runner seems to have the problem of falling back to run a single JUnit 3 test.
So…the solution is quite simple:
Now the problem is gone and the test-driven developers are happy :-).