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

Explore better Junit testing experience (brainstorm) #1344

Closed
Tracked by #889
nickzhums opened this issue Oct 18, 2021 · 5 comments · Fixed by #1354
Closed
Tracked by #889

Explore better Junit testing experience (brainstorm) #1344

nickzhums opened this issue Oct 18, 2021 · 5 comments · Fixed by #1354
Milestone

Comments

@nickzhums
Copy link
Member

Theme: Testing

@nickzhums

This comment has been minimized.

@nickzhums

This comment has been minimized.

@jdneo jdneo transferred this issue from microsoft/vscode-java-pack Dec 2, 2021
@jdneo jdneo added this to the 0.34.0 milestone Jan 13, 2022
@jdneo
Copy link
Member

jdneo commented Jan 20, 2022

When the workspace contains only an unmanaged folder project and no test framework is found on the project's classpath, then the user will see this button in the Testing explorer to enabling Java tests.

enable-test.mp4

@nickzhums
Copy link
Member Author

Thanks! Another thought from me is to generate an empty test class for them, which will complete the e2e journey.
But Let's wait for some user feedback first

@jdneo
Copy link
Member

jdneo commented Jan 20, 2022

@nickzhums Good idea! We can explorer further for sure.

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

Successfully merging a pull request may close this issue.

2 participants