Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 415698

Summary: [JUnit] No effect of "Rerun Test - Failures First" on top-level suites/tests
Product: [Eclipse Project] JDT Reporter: Moritz Eysholdt <moritz.eysholdt>
Component: UIAssignee: JDT-UI-Inbox <jdt-ui-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: manju656
Version: 4.4   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard: stalebug
Attachments:
Description Flags
failed reordering none

Description Moritz Eysholdt CLA 2013-08-22 11:55:11 EDT 
Steps to reproduce:

1. create a Java Projekt
2. create two or more JUnit4 tests within this project, at least one of the tests should be failing.
3. run all tests by doing a right mouseclick on the project and choosing "Run As -> JUnit test" from the context menu. Do NOT use a test suite.
4. make sure the failing test is executed last.
5. click on "Rerun Test - Failures First"

Observed behaviour:
- within the test classes, the failing tests cases are rerun first.
- the test classes are executed in the same order.

Expected behaviour: Test classes/suites with failing tests should be executed first.

Workaround: 
Use a JUnit suite to compose the tests. Don't let the JDT JUnit launch configuration collect the tests classes.
Comment 1 Moritz Eysholdt CLA 2013-08-22 11:56:07 EDT 
Created attachment 234669 [details]
failed reordering
Comment 2 Martin Mathew CLA 2013-08-23 00:21:27 EDT 
Reproducible using Eclipse Build id: I20130804-2300.
Similar issue is mentioned in bug 140392#c11
Comment 3 Eclipse Genie CLA 2020-03-17 03:02:00 EDT 
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.