Bug 202162 - [JUnit] Rerun failure first junit test does not do failing test first
Summary: [JUnit] Rerun failure first junit test does not do failing test first
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P5 minor with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-04 11:10 EDT by Benno Baumgartner CLA
Modified: 2022-06-05 00:14 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Benno Baumgartner CLA 2007-09-04 11:10:43 EDT 
I20070828-0800

1. Open CleanUpTest
2. Change last tests expected result such that it will fail
3. Run As>Junit Plugin test
4. when done: Rerun - failures first
5. Stop before done
6. Rerun test
Is:
 Label says something like 'Launching Rerun (failed test first)' but the failed test is executed last.
Should:
 Either change label or run failing first
Comment 1 Chris Simmons CLA 2011-11-10 12:48:47 EST 
Presumably this was never fixed when fixing bug 102632?
Comment 2 Markus Keller CLA 2011-11-10 13:03:40 EST 
> Presumably this was never fixed when fixing bug 102632?

Rerun failed first indeed didn't work with JUnit 4 initially, but this has been fixed with bug 140392.


This bug is not about JUnit 4. It's about a bad label for a test run in a specific scenario:

- run tests
- Rerun Test - Failures First
- Rerun Test
=> the label for the last test run includes "(Failed Tests first)", although it ran in normal order
Comment 3 Eclipse Genie CLA 2020-06-02 17:57:20 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.

If you have further information on the current state of the bug, please add it. 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.
Comment 4 Eclipse Genie CLA 2022-06-05 00:14:32 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.

If you have further information on the current state of the bug, please add it. 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.