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)
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_suitewith 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)