Description Caspar D. 2010-09-03 01:56:13 EDT

When using the JUnit4 test runner to run a test suite that contains a
few nested test suites, each of which contains the *same* set of test
classes, the JUnit view repeatedly updates the bottom-most occurrences
of the test class elements in the tree view, and fails to update the
other ones when they are executed (which they are).

The problem doesn't occur when using the JUnit3 test runner.

I'll attach a test project demonstrating the problem in a minute.

(In case anyone wonders what the point is of including the same test
classes several times: I configure each instance differently by passing
a config object from the suite that contains them; see forthcoming
attachment.)