On Wed, Sep 5, 2018 at 8:39 AM Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: > So let's hear some ideas how to improve the situation, m'kay? > Just as a reminder, this is the problem I want to solve: I want to run the > tests in a light-weight manner, with minimal output, and only in case of > an error do I want to crank up the verbosity. Instead of wasting most of the > effort to log everything and then throwing it away in most of the common > cases, I suggest to re-run the entire test. What about the very different approach of capturing the full "verbose" output the executed tests in addition to whatever is actually output to the terminal? If a test fails, then (and only then) you can insert the captured verbose output into the JUnit XML file. This way (if we always have the full verbose output at hand), you don't need to re-run the test at all. I've cc:'d Peff and Jonathan since I believe they are more familiar with how all the capturing / output-redirection works in the test suite.
