New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JUnit5 integration results in "1 containers skipped" #371

Closed
estekhin opened this Issue Dec 13, 2016 · 0 comments

Comments

2 participants
@estekhin

estekhin commented Dec 13, 2016

Using JUnit5 M3, JMockit 1.29.

After running the tests I got statistics similar to this:

Test run finished after 14125 ms
[       435 containers found      ]
[         1 containers skipped    ]
...

That "1 containers skipped" is due to

executionListener.executionSkipped(descriptor, null);
.

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()).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment