Report problematic selector resolution results as discovery issues #4389
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.
Overview
Instead of aborting test discovery on the first problematic selector
resolution result, they are now converted to discovery issues with
ERROR
severity and reported during execution.Issue: #242
I hereby agree to the terms of the JUnit Contributor License Agreement.
Definition of Done
@API
annotationsChange is documented in the User Guide and Release Noteswill be done in a later PR