Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 314596 - [JUnit] junit view can't correctly report the test result if executing a case many times in a test suite
Summary: [JUnit] junit view can't correctly report the test result if executing a case...
Status: CLOSED DUPLICATE of bug 172256
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-26 22:34 EDT by Meng Xin Zhu CLA
Modified: 2010-05-27 10:53 EDT (History)
3 users (show)

See Also:


Attachments
screen shot of junit view (155.08 KB, image/png)
2010-05-26 22:38 EDT, Meng Xin Zhu CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Meng Xin Zhu CLA 2010-05-26 22:34:44 EDT
My program has some issues on multiple thread, so a test case intermittently failed in daily automation testing.
So I create a test suite and then add the same case in that suite many times to reproduce the failure.

Below is the code snippet to create the test suite,

@RunWith(Suite.class)
@SuiteClasses({
	BasicSetupLogTests.class,
	BasicSetupLogTests.class,
	...
	BasicSetupLogTests.class,
	BasicSetupLogTests.class})
public class SetuplogTestSuite {
//
}

After running the test suite, junit view can correctly report the test result for each case even if they are same.
Comment 1 Meng Xin Zhu CLA 2010-05-26 22:38:04 EDT
Created attachment 170130 [details]
screen shot of junit view

If some running of the case are failure, the junit view just reports the final result as failure. It can't tell me which one is failed and how many cases are failed. It can't report the stack of failure.
Comment 2 Dani Megert CLA 2010-05-27 03:30:05 EDT
Looks like a duplicate of bug 172256.
Comment 3 Markus Keller CLA 2010-05-27 10:53:44 EDT

*** This bug has been marked as a duplicate of bug 172256 ***