-
Notifications
You must be signed in to change notification settings - Fork 291
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
[BUG] "testing.openTesting": "openOnTestFailure" opens the Test Results viewlet every test suite run, instead of only on failures #1118
Comments
GeorgeWL
changed the title
[BUG]
[BUG] "testing.openTesting": "openOnTestFailure" and opens Test Results viewlet every time, instead of only on failures
Feb 21, 2024
GeorgeWL
changed the title
[BUG] "testing.openTesting": "openOnTestFailure" and opens Test Results viewlet every time, instead of only on failures
[BUG] "testing.openTesting": "openOnTestFailure" opens the Test Results viewlet every test suite run, instead of only on failures
Feb 21, 2024
#1119 seems to have mostly fixed it, my only curiosity, is there a way to have it auto-close when tests begin succeeding again, or is that not something the vscode API gives access to? |
Yes, there is a command to close the panel, but neither vscode nor this extension implemented the auto "closing" logic. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I tried setting "testing.openTesting": "openOnTestFailure" and the Test Results viewlet still opens every time, instead of only on failures
To Reproduce
Steps to reproduce the behavior:
Note: A sample repo will help us identify the bug much faster. 🙏
Expected behavior
A clear and concise description of what you expected to happen.
Viewlet only opens on failures, if all are successful, no Test Results viewlet is shown
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
node -v
: LTSnpm -v
oryarn --version
: LTSyarn test
on-save
Prerequisite
yarn test
Additional context
Add any other context about the problem here.
The fastest (and the most fun) way to resolve the issue is to submit a pull request yourself. If you are interested, please check out the contribution guide, we look forward to seeing your PR...
The text was updated successfully, but these errors were encountered: