eclipse-jdt / eclipse-jdt/eclipse.jdt.ui
JUnit runner misses inner classes when run as source folder
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 59
- Forks
- 127
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 37
Description
When running all JUnit5 tests with the "run all tests in the selected project, package or source folder" whether inner classes are discovered depends on whether you select a package (finds them) or source folder (misses them)
Consider this project JUnit5Discovery.zip and run JUnit5 tests on "src" and only 2 tests are run, but on package "example" 6 tests are run.
"src" version
"example" package version
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached JUnit5Discovery.zip project and reproduce the difference by running JUnit 5 tests on the src source folder and the example package. Trace the source-folder and package discovery paths, then verify that both selections discover all six tests, including inner classes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100