P4
Javatest 4.2 (applicable to earlier versions as well).
TestSuite code has means to inform Harness that test execution has been started. This is done via call to com.sun.javatest.TestRunner.notifyStartingTest(TestResult). One of observers to this info is Progress Monitor window that adds started tests to the list of "Tests In Progress".
Theoretically noone forbids TestSuite's implementation to start one test multiple times. For example if test has crashed in the middle and implementation would like to repeat it. Thus a TestSuite may call TestRunner.notifyStartingTest(TestResult) several times for one TestResult. Harness should behave well in such scenario.
Currently ProgressMonitor/TestsInProgress window adds Test to "active list" for the 2nd time, but removes it only once when TestRunner.notifyFinishedTest(TestResult) is called. So - one line stays there until the end of a test run.
This should be changed - ProgressMonitor/TestsInProgress window should not add test to list of "active" if it's already there.
TestSuite code has means to inform Harness that test execution has been started. This is done via call to com.sun.javatest.TestRunner.notifyStartingTest(TestResult). One of observers to this info is Progress Monitor window that adds started tests to the list of "Tests In Progress".
Theoretically noone forbids TestSuite's implementation to start one test multiple times. For example if test has crashed in the middle and implementation would like to repeat it. Thus a TestSuite may call TestRunner.notifyStartingTest(TestResult) several times for one TestResult. Harness should behave well in such scenario.
Currently ProgressMonitor/TestsInProgress window adds Test to "active list" for the 2nd time, but removes it only once when TestRunner.notifyFinishedTest(TestResult) is called. So - one line stays there until the end of a test run.
This should be changed - ProgressMonitor/TestsInProgress window should not add test to list of "active" if it's already there.