Vscode-java-test: Navigate from stacktrace line to proper file in test results
Following up on #306, we need better navigation from the report to java files. Since this is gonna be more complicated I'm opening it in a separate ticket: I'd be nice if the generated stacktraces actually linked to matching lines from source code, to make it possible to navigate directly from the report to any file, in the workspace or the classpath, involved in the test failure, as with other Java IDEs.
fbricon
All 5 comments
+1 Is there any other solution to navigate the stack trace file now? while we could not click file on it.
jkryanchou
on 9 Dec 2019
@jdneo Could you redirect the stack trace to the DEBUG CONSOLE in order that we could click the stack trace file through the panel? Or we have no other way to navigate it quickly.
jkryanchou
on 10 Dec 2019
This is a must have when refactoring tests. Not being able to go to places where the exception is being thrown in an easy way it's time consuming and puts VS Code in a serious disadvantage against IntelliJ or Eclipse when developing Java.
getaceres
on 16 Dec 2019
Bumping this issue again, this is a major blocker in moving from IntelliJ to VS Code.
Skynet0
on 28 May 2020
This is available in 0.26.0 (with Language Support for Java(TM) by Red Hat upgrade to 0.70.0).
jdneo
on 9 Nov 2020
Related issues
oakad
路
9Comments
ashoknailwal
路
8Comments
hrsto
路
4Comments
Gueka
路
3Comments
mccreery
路
4Comments
Most helpful comment
This is a must have when refactoring tests. Not being able to go to places where the exception is being thrown in an easy way it's time consuming and puts VS Code in a serious disadvantage against IntelliJ or Eclipse when developing Java.