Sheng Chen
Sheng Chen
@OneBigOwnage VS Code team released `1.40.0` recently. Is this problem still occur in `1.40.0` on your side?
@rajkundu Is it working on VS Code 1.40.0 with Test Runner 0.21.0?
Ok so here is the solution for those people who cannot run JUnit 5 from the Invisible project(dependency managed in `lib` folder): 1. Update VS Code to 1.40.0 2. Update...
@moinessim Have you tried [this](https://github.com/microsoft/vscode-java-test/issues/859#issuecomment-552433039) solution?
@hc2683 Maybe adding a setting to turn on/off persisting the launch configuration into launch.json when executing tests? What do you think?
We have commands to run/debug tests in current file or at current cursor position:  Will they meets your requirement?
I see. One more question: would you mind explaining the reason for running from command line via maven, instead of the testing ui? Is that because the testing ui has...
> I don't like the peek view of the failed test. too intrusive. Jumping from the stacktrace to files is also clunky. The peek view is controlled by VS Code...
> Intrusive is that it gets in the way of code, has a different scrolling context. Clunky: let's say there's an assertion failure in a test. I expand the peek...
> It's doable to relax matching rules and apply them to other log lines. @testforstephen should I file an issue for this in debug repo? Or you prefer to track...