junit5 icon indicating copy to clipboard operation
junit5 copied to clipboard

Published 20 hours ago • verified publisher icon junit-team

Introduce support for rerunning failed tests first

Open jonnytest1 opened this issue 5 years ago • 11 comments

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

  • Used versions (Jupiter/Vintage/Platform):
  • Build Tool/IDE: eclipse 2019-03 and previous

Deliverables

jonnytest1 avatar Mar 28 '19 13:03 jonnytest1

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?

marcphilipp avatar Mar 28 '19 14:03 marcphilipp

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

jonnytest1 avatar Mar 28 '19 17:03 jonnytest1

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?

marcphilipp avatar Mar 29 '19 07:03 marcphilipp

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

noopur2507 avatar Mar 29 '19 08:03 noopur2507

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

jonnytest1 avatar Mar 29 '19 08:03 jonnytest1

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.

noopur2507 avatar Mar 29 '19 09:03 noopur2507

Tentatively slated for 5.5 M2 for team discussion

sbrannen avatar Mar 29 '19 09:03 sbrannen

Related Stack Overflow question

sbrannen avatar Apr 13 '19 12:04 sbrannen

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 ^^

jonnytest1 avatar Mar 19 '21 17:03 jonnytest1

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.

stale[bot] avatar Jun 19 '22 20:06 stale[bot]

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.

kuniss avatar Jul 01 '22 13:07 kuniss