I am not sure what the correct semantics should be in that case, but "skipped container" looks somewhat baffling when there are no tests or tests classes explicitly marked as skipped or disabled, and the test suite is green.
Please consider replacing executionSkipped() with a sequence of executionStarted() immediately followed by executionFinished(..., TestExecutionResult.successful()).
The text was updated successfully, but these errors were encountered:
Using JUnit5 M3, JMockit 1.29.
After running the tests I got statistics similar to this:
That "1 containers skipped" is due to
jmockit1/main/src/mockit/integration/junit5/JMockitTestEngine.java
Line 53 in 0555670
I am not sure what the correct semantics should be in that case, but "skipped container" looks somewhat baffling when there are no tests or tests classes explicitly marked as skipped or disabled, and the test suite is green.
Please consider replacing
executionSkipped()
with a sequence ofexecutionStarted()
immediately followed byexecutionFinished(..., TestExecutionResult.successful())
.The text was updated successfully, but these errors were encountered: