The redirectTestOutputToFile does not handle output before tests, nor does it handle capturing output on both streams

The redirectTestOutputToFile feature does not handle cases when output is soaked up before the tests actually run, like output from static blocks or from test case constructors. If output is detected before the testSetStarting is invoked, then all further output will be due to a thrown ISE, which gets eatten up somewhere in surefire.

Additionally, when a test outputs to STDOUT and STDERR, the output is not muxed properly into the -output.txt file.