Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider redirect the test stack trace into the debug console #903

Closed
jkryanchou opened this issue Dec 10, 2019 · 18 comments
Closed

Consider redirect the test stack trace into the debug console #903

jkryanchou opened this issue Dec 10, 2019 · 18 comments

Comments

@jkryanchou
Copy link

I run a test case raise a exception on stack trace in the test report while I could not see the whole filename on it. While in the IDEA, I could see the whole stack trace. in de debug console.
Could author redirect the stack trace into the debug console? it also could navigate the stack trace file through the debug console panel.

image

@jdneo
Copy link
Member

jdneo commented Dec 10, 2019

There is a scroll bar at the bottom of the view.

@jkryanchou
Copy link
Author

@jdneo I knew this is a up-down scroll bar, while I couldn't see the right part which show the exact line of file. the stack trace show the whole information of exceptions or omit some part.

@jkryanchou
Copy link
Author

@jdneo Is there any settings I could configure redirect the exception into DEBUG CONSOLE. or Output. I could view the whole stack trace info.

@jdneo
Copy link
Member

jdneo commented Dec 10, 2019

Sorry there is no such setting for now. Will consider to add the ability to redirect it into debug console.

@jdneo jdneo changed the title Cannot see the file on the top of stack trace. Consider redirect the test stack trace into the debug console Dec 10, 2019
@jkryanchou
Copy link
Author

@jdneo Would the feature release in next version? Be eager to see the feature in next release. Because there is no other way to help me out within the VSCode.

@jkryanchou
Copy link
Author

  1. Redirect to the Debug Console
  2. The stack trace file could be clickable to the file location such as DEBUG CONSOLE panel.

@jkryanchou
Copy link
Author

@jdneo Could it be released in 0.22.0?

@jdneo
Copy link
Member

jdneo commented Dec 16, 2019

I cannot say a definite time or version of when this feature get released for now. But it's on our radar.

Meanwhile, if you want to contribute for this feature, you can just send out the PR.

Thanks.

@jkryanchou
Copy link
Author

@jdneo I got it. If time available. I will.

@jdneo
Copy link
Member

jdneo commented Dec 17, 2019

Thanks @jkryanchou,

IMO, I prefer to support navigate from the stacktrace instead of redirect the output into the debug console, since it will ruin the program's own output.

If you want to implement navigating from the stacktrace, here is a reference of the debugger's Java implementation: https://github.com/microsoft/java-debug/blob/ac7d26bcfd5736f2cabd93f2bc065aa8ff302088/com.microsoft.java.debug.core/src/main/java/com/microsoft/java/debug/core/adapter/handler/LaunchRequestHandler.java#L256-L280

Meanwhile, I'll ask the team if it is possible to let either Debugger or Language Server to expose the related API for navigating from the stacktrace. If we have this API, things would be much easier.

@jdneo
Copy link
Member

jdneo commented Dec 17, 2019

Related issue in language server eclipse-jdtls/eclipse.jdt.ls#1202

If we have this API in language server, both Debugger and Test Runner can leverage it.

@jkryanchou
Copy link
Author

@jdneo Got it. Thanks. If I could navigate the traceback in DEBUG Console. it could be link to the proper file location easily.

@jdneo
Copy link
Member

jdneo commented Dec 17, 2019

@jkryanchou I still not prefer redirecting the stacktrace to debug console. This will ruin the program's output. We should enable the feature in the test report.

@jkryanchou
Copy link
Author

@jdneo OK.

@jdneo
Copy link
Member

jdneo commented Nov 9, 2020

Now it's supported to navigate from stracktrace to source location in 0.26.0 (with Language Support for Java(TM) by Red Hat upgrade to 0.70.0).

Is this solved your problem @jkryanchou?

@no-response
Copy link

no-response bot commented Nov 23, 2020

This issue has been closed automatically because it needs more information and has not had recent activity. Please reach out if you have or find the answers we need so that we can investigate further.

@no-response no-response bot closed this as completed Nov 23, 2020
@jkryanchou
Copy link
Author

@jdne OK I will try it later.

@no-response no-response bot reopened this Mar 3, 2021
@jdneo
Copy link
Member

jdneo commented May 7, 2021

Close since being inactive for a long time. Please let me know if you have any concerns.

@jdneo jdneo closed this as completed May 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants