Parallel Execution: Output from junit.framework.TestListener.endTest() is swallowed

The reason for this behaviour seems to be as follows:

In class ConcurrentPrintStream.write(byte[], int, int), TestMethod.getThreadTestMethod() returns null when the endTest()-statement from the TestListener is printed. In this case, printing is delegated to the ByteArrayOutputStream out, which is never printed.

Made a partial fix in r962846

Console output is now not discarded, The "static" output from a test run is output at the end, and in no particular order wrt the test methods.

It should be possible to improve this, most notably for run-mode "classes" it should be possible to attach the TestSet to the Thread much the same way as we attach the TestMethod. For "methods", it seems like all the static test methods are run sequentially on the main thread before threading is started, so it should possible to record and associate this with the correct test. As for "both" I think the best that can be done is to do /all/ the beforeclass stuff before the test run and all the afterClass stuff after the test runs.

I will gladly review any patches received to further improve this. The IT for surefire-628 should be extendable to verify the proper order.

Anyone wishing to experiment with this can do the following:

In directory:
surefire/surefire-integration-tests/src/test/resources/surefire-628-consoleoutputbeforeandafterclass

Run commands tests like this:
mvn -Dsurefire.version=2.6-SNAPSHOT -Djunit.parallel=methods clean test
mvn -Dsurefire.version=2.6-SNAPSHOT -Djunit.parallel=classes clean test

You should be able to test & observe the effects of any patch

Deployed updated 2.6-SNAPSHOT

We are unable to do anything about output that is not associated with a test because making assumptions about this would have severe implications for embedded use. Therefore, test output that cannot be associated with a testcase will just float right out to the console and the fix that was made for 2.6 is the end of this issue.