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

Test output not showing #344

Open
benliddicott opened this Issue Oct 15, 2018 · 11 comments

Comments

Projects
None yet
8 participants
@benliddicott

benliddicott commented Oct 15, 2018

Ouput pane does not show test output, seems to be happening since version 0.10.0 and/or the latest VSCode update, running in conjunction with the Microsoft Java Extension Pack 0.4.0.

  • Java: Show test output does not work.
    It selects the Output pane and selects "Test Output" in the dropdown, but no test output is visible.

  • Java: Open Log works and shows that the test output has appeared in the log

  • This is reproducible from a Maven project built using the maven archetype-quickstart-jdk8 archetype.

@lwl19

This comment has been minimized.

lwl19 commented Oct 17, 2018

The same issue, test output panel is not working.

@IMEVER

This comment has been minimized.

IMEVER commented Oct 17, 2018

I have the same issue with version 1.27 and 1.28 under deepin linux

@jdneo

This comment has been minimized.

Member

jdneo commented Oct 19, 2018

@benliddicott @lwl19 @IMEVER

I found it very wried because if I disable the Maven extension, the output will just be fine. But if the Maven extension is enabled, the test output cannot be shown in the output channel.

Could you please have a try and let me know if it is just the same as what I said on your side?

@IMEVER

This comment has been minimized.

IMEVER commented Oct 19, 2018

@jdneo Yes, it works. When disable maven extension from workspace, reload vscode, run test, I can see test output right there.

@jdneo

This comment has been minimized.

Member

jdneo commented Oct 19, 2018

Hmm, Don't know who to blame for now. 😵 Let me investigate.

@cpdupuis

This comment has been minimized.

cpdupuis commented Oct 20, 2018

I do see the test output when I click on the red X for a failed test in the editor pane (at least the assertion message and stack trace) when I use junit 4.12. When I use org.junit.Jupiter 5.3.1 and org.junit.platform 1.3.1, no output is shown at all when I click on the red X.

@AzureLithium

This comment has been minimized.

AzureLithium commented Oct 21, 2018

I do see the test output when I click on the red X for a failed test in the editor pane (at least the assertion message and stack trace) when I use junit 4.12. When I use org.junit.Jupiter 5.3.1 and org.junit.platform 1.3.1, no output is shown at all when I click on the red X.

I'm using org.junit.Jupiter 5.3.1 and org.junit.platform 1.3.1 and I can see the test output in the "Test Output" window whether the test passes or fails, doesn't matter, but that is if I have disabled the "Maven for Java" extension just as @jdneo said. If I don't disable that extension, "Test Output" window is always blank.

Definitely a bad interaction between these two extensions.

@xiaoxiaobingguai

This comment has been minimized.

xiaoxiaobingguai commented Oct 22, 2018

I have the same problem。How to resolve?

@jdneo

This comment has been minimized.

Member

jdneo commented Oct 24, 2018

I'm refactoring the test runner extension these days. Hopefully, this issue could be resolved after the new version releases.

@myguddy

This comment has been minimized.

myguddy commented Oct 31, 2018

Suggestion !

After disable maven I can see test logs in vscode output panel.

However, there are bunch of logs mixing of log from junit and user std output.
I am not sure of inside architecture of this extension( I love this thanks).

Why don't we separate the log data into junit log and std output from java code, System.out.print ?
So programmer can check test result quickly.

Thanks for your work done so far.

@jdneo

This comment has been minimized.

Member

jdneo commented Oct 31, 2018

@myguddy That's a good suggestion. Adding a tracking issue here: #358

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment