Community
Participate
Working Groups
While running big JUnit tests, I would like to see which test produces which output to the console (especially: if line A still belongs to test 1 or already to test 2). I see these possible solutions: 1. Eclipse remembers for every line of output in the console where System.out was called (similar to the "go to source line of stack trace"). This would be a very nice feature when I wonder "where did this output came from!?" but somewhat expensive (memory/runtime). 2. When I select a test case in the JUnit frame, eclipse either scrolls to the first line of output, highlights the output printed during that test or hides the output of all other tests. 3. Solution #1 can be enabled with an option in the context menu of the console and/or the preferences. Solution #2 is always active when JUnit tests are run. Solution #1 would be expensive (lots of stack-traces to analyze and a lot of pointers to the source) but very comfortable. Solution #2 would be much more simple (basically, the JUnit test runner could copy the output of the console or add markers to the output) but limited to JUnit runs. Of course, I would prefer #3 :-)
Not for 3.0.
Since there was some work on JUnit 4.0, I wanted to ask if this feature can be reconsidered.
sorry, we won't have time for such a feature
Can this be considered for 3.3? IntelliJ IDEA automatically cuts the test outputs in their console which is really neat. Another solution might be to have a "redirect" option in the prefs so output of tests can be logged somewhere without having to build custom IO handlers. Clicking on the tests could then offer to open these logs in an editor.
We still have no plans for this feature. Help is welcome. Please do not reopen bugs, just add comments, and we will reopen if the situation changes.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
Reopening as we got another request for this.
*** Bug 543550 has been marked as a duplicate of this bug. ***
Making the JUnit listener keep track of current line number in console when test start and stop could be enough here; then we could have an action (right click or link) to "show related console log".
A fun thing is that Jenkins manages to to it. The XML reports generated by JUnit do contain the standard output/error and Jenkins renders them.
