Take Java JUnit conventions into account when detecting test files to upload #550
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.
I've just discovered the test upload feature - great work!
I've tried it on a Maven/Java project and the majority of my test files were not detected because Maven/JUnit/Surefire prefixes them with
TEST
and nottest
.https://github.com/opentripplanner/OpenTripPlanner/actions/runs/11665161617/job/32477225744
For this reason I'm adding this to the default patterns for Junit test uploads.