Prevent removal of ErrorSpecNode by Maven #1447
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1444.
At the moment,
SpockEngineDiscoveryPostProcessor#processSpecNode
creates anErrorSpecNode
(which implementsorg.junit.platform.engine.TestDescriptor
) after catching errors thrown by extensions, which is then silently discarded by Maven Surefire because it filters fortestPlan.containsTests()
. Therefore, we have to make sure thatcontainsTests
returnstrue
. An easy way to do that is to overridemayRegisterTests()
. Another way would be to overrideisTest()
instead, but actually neither an error node nor a spec actually is as test, they rather can contain tests.