Community
Participate
Working Groups
1. Run a couple of unit tests which compare Strings with assertEquals(). Make sure one of the test fails with an error. 2. Run the tests and open the string compare view 3. Fix the comparison error and throw an exception instead. 4. Run the tests again The compare view will still show the content from the run in step #2. If you don't read the error message in the "Failure Trace", it's easy to get confused why the error doesn't vanish. Suggested fix: Clear the compare view after running the unit tests when the first error in the JUnit view doesn't use assertEquals(String, String).
Agree it should be cleared on on rerun.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
