When you run a test case with vscode-java-test within code-server the message and stacktrace does not show up for the test case. However the report says wether the test case passed/failed. (Gradle with JUnit5)
Note: To install vscode-java-test in code-server; the regular installation through GUI seems to broken; you will have to follow instructions from this dockerfile to download the java pack manually before opening code-server.
Hi @rohinwork,
Would you mind to share some screenshot to us?
Hi @jdneo,
Sure here you go:

I could also provision a temporary code-server workspace if you would like to debug.
Thanks for your continued support on this! :)
Thank you @rohinwork.
The test report is actually an HTML page and gets rendered by VS Code's webview. And I guess what you are encountering is that the report cannot be expanded.
If that is the case, then I think this should be a bug/issue of Code Server. What we can do from the extension side is really limited since we are just using the API provided by VS Code itself.
Hi @jdneo
I looked around a little bit more and found out that there is no output in Java Test Runner View. Would this indicate that there is a problem with the extension not capturing/receiving any output?
Are there any files you would like me to look at in the workspace?
Local Setup:

Code-Server Setup:

Thank you,
Rohin
I see. What's the value of the setting java.test.log.level in your code server?
@jdneo sorry my bad. I set it to verbose on remote machine and now I am able to see the logs. However logs are visible without this setting on my local machine.
On remote machine, even after I made this change I am not able to see the stacktrace in the test report. Is there someplace where this report is getting persisted, if so, I could manually check it out.
Quick aside question:
Whenever I try to setup this extension in debug mode (locally) I have a few problems

Thanks for your prompt responses :)
However logs are visible without this setting on my local machine.
This is because the setting has the default value:info
For the two questions, you asked. I guess your project is neither a Maven project nor Gradle project. Am I right?
@jdneo It is a gradle project actually. So here's what's happening
Have you run npm run build-plugin?
Yes I have actually. I am able to set breakpoints within the code and debug as well. Is there a possibility for you to check if this is working for you locally with a fresh clone of the repo and a new project with spring initializer
Here's a recap of what I did:
I did not setup eclipse and other tools since I only want to debug the typescript part of this repo as mentioned in the repo.
Thank you for reporting this. I have to apologize for that there is a step missing in the contributing page.
I have updated the docs in this PR: https://github.com/microsoft/vscode-java-test/pull/705
@jdneo No problem 馃憤and thank you for the update.
This aside, I am still not able to this up and running on code-server the right way.
Another observation that I made was that if I set the logger level to info (manually) on my remote machine; no logs show up on the output window. However, only when I set it to verbose the right logs are showing up with stacktrace, etc which means that the HTML that you are generated should be working fine?
If I was to file to a bug with the code-server team. Do I have to tell them anything more to give them more context on this issue?
I would again like to thank you very much for your quick and continued support on this :)
info is only to show the application's output. For example. in your code, you write system.out.printlin("hi").
I think the problem is that code server has some problem for rendering the webview, causing that the test report cannot be expanded.
Hi @jdneo, I am Sridher, Rohin's colleague.
Awesome to see such quick replies/commitment for an open-source project from a Microsoft employee :+1: . That's definitely unheard of in the past :)
Hi @sridherj,
We are embracing the open-source world 馃槂. Nice to meet you!
@jdneo Thanks for clearing that up. Raised an issue on the code-server repo here.
Closing this one and watch on the upstream issue.