bazel-contrib / bazel-contrib/rules_jvm
java_test_suite doesn't link back for parameterised tests
- Dominant language
- Go
- Stars
- 54
- Forks
- 98
- Avg merge
- 6d 2h
- Merged PRs (30d)
- 7
Description
Sorry if this is the wrong place, but it's sometime hard to guess where the responsibility for certain functionality sits.
I've written a set of unit tests in my bazel java project, and I'm using `java_test_suite` with JUNIT5 so that I can run these tests in my IDE.
If a test fails, you usually double-click the failing test in the report window to jump to the source code for that test, it would normally jump to either the method, or the failing assertion.
Some tests are `@ParameterizedTest`, and these tests don't allow you to click them to get back to the source code, even though they should at least go to the test method responsible.
Is there anything that can be done about this?
Please advise if this missing functionality belongs elsewhere (like the intellj bazel plugin etc)
Contributor guide
Research direction
Start by reproducing the failure-link behavior with java_test_suite, JUnit5, and a @ParameterizedTest in a Java project. Trace whether the missing source link comes from the test reporting produced by java_test_suite or the IntelliJ Bazel plugin; done means a parameterized test failure links back to its test method.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, developer-experience, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100