search

junit-team / junit5

✅ The 5th major version of the programmer-friendly testing framework for Java and the JVM
https://junit.org
Eclipse Public License 2.0
6.43k stars 1.49k forks source link

Introduce support for rerunning failed tests first #1838

Open jonnytest1 opened 5 years ago

jonnytest1 commented 5 years ago

the button in he JUnit eclipse view that says rerun failed first does nothing different than the one right next to it (rerun) please either remove or preferably fix its functionality

Steps to reproduce

run tests that fail click rerun failed first no change in order

Context

Deliverables

marcphilipp commented 5 years ago

This would be an interesting use case for test ordering which was introduced in JUnit 5.4.

@jonnytest1 Could you please report an issue with Eclipse and link it here?

jonnytest1 commented 5 years ago

@marcphilipp its not really an eclipse issue though is it ? oO but which category

marcphilipp commented 5 years ago

Let's say it involves both parties and I'm not sure how Eclipse has implemented it for JUnit 4.

@noopur2507 Do you have time to take a look?

noopur2507 commented 5 years ago

This was initially discussed in #884. Do we have a corresponding API now where a comparator can be passed?

jonnytest1 commented 5 years ago

I made a bug report at eclise bugs (I hope this is as imagined ) https://bugs.eclipse.org/bugs/show_bug.cgi?id=545916

noopur2507 commented 5 years ago

I made a bug report at eclise bugs (I hope this is as imagined ) https://bugs.eclipse.org/bugs/show_bug.cgi?id=545916

Thanks, I have updated it.

sbrannen commented 5 years ago

Tentatively slated for 5.5 M2 for team discussion

sbrannen commented 5 years ago

Related Stack Overflow question

jonnytest1 commented 3 years ago

quick update into the group as the eclipse bug just got closed by their automatic bugtracker i think in the meantime the button got greyed out with no functionality - which to be honest doesnt really solve the problem ^^

stale[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. Thank you for your contribution.

kuniss commented 2 years ago

Just for better argumentation: This would really be a helpful feature as not all tests run such fast as the unit test theory intends it. 😄 E.g., we have JUnit tests which run against HW devices which are quite slow. Having the possibility to re-run failed tests only would make our development faster in the sense of getting less and less failed test and finally make a re-run for all.