Stop reporting discovery issues for synthetic methods #5103
+75
−3
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.
Prior to this commit, all methods of a potential test class were
checked for being test methods, including synthetic ones. However, when
resolving a test class only non-synthetic methods were taken into
account.
Since the Kotlin compiler generates a synthetic, static method suffixed
with
$suspendImplfor every open (i.e. non-final) method and copiesits annotations, such methods were included in the check.
In addition to filtering out synthetic methods from being checked,
KotlinReflectionUtilsno longer recognizes them as suspend functions.Fixes #5102.
I hereby agree to the terms of the JUnit Contributor License Agreement.
Definition of Done
@APIannotations