Prevent test methods incorrectly defined as Kotlin top-level functions from being considered for test execution #325
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.
This won't work, as JUnit 5 doesn't actually run these methods. However, if a runner is created for the class, then there is a mismatch between Android's expectations and JUnit 5's deliverables. This messes up Android's internal test counting, causing issues like "Expected N+1 tests, received N".
This resolves #316 and may be a first indicator towards solving #298.