You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using the latest beta 5.0 to obtain the support for Before/After Class. When we want to run exactly a specific test method of a test suite from eclipse IDE for example we got that all test are executed. The same issue happens in maven when the rerun feature is enabled. The point is that when we got a failure all tests in the test suite are re-executed. This means increase build time and sometimes the failure of test flaky that was passed on the first run.
The root cause is that the list of filtered out methods are not passed when the OSGi service junit invoker is called. Unfortunally when a filter (I mean a simple method descriptor filter) is applied to the JUnitCore instance it apply this filter internally saving the filtered list of descriptor that must be executed. This internal state is not accessible and this means is not possible to move forward to the OSGi service container.
Affects: 5.0.0, 4.13.1
Votes: 0, Watches: 1
The text was updated successfully, but these errors were encountered:
Nikolas Falco created PAXEXAM-930
We are using the latest beta 5.0 to obtain the support for Before/After Class.
When we want to run exactly a specific test method of a test suite from eclipse IDE for example we got that all test are executed. The same issue happens in maven when the rerun feature is enabled. The point is that when we got a failure all tests in the test suite are re-executed. This means increase build time and sometimes the failure of test flaky that was passed on the first run.
The root cause is that the list of filtered out methods are not passed when the OSGi service junit invoker is called.
Unfortunally when a filter (I mean a simple method descriptor filter) is applied to the JUnitCore instance it apply this filter internally saving the filtered list of descriptor that must be executed. This internal state is not accessible and this means is not possible to move forward to the OSGi service container.
Affects: 5.0.0, 4.13.1
Votes: 0, Watches: 1
The text was updated successfully, but these errors were encountered: