Warn the user when testing configuration is not complete
See original GitHub issueOn behalf of @qubitron
Repo: github.com/qubitron/hello-stackoverflow
Scenario 1
- Enable unit tests (do not configure the args)
- Running and discovering tests fail
Suggestion: Check if args are empty, if they are, then display a prompt to configure test framework
~Other errors~
- ~Testing with PyTest failed~
- ~Debug adapter failed regularly leaving extension in a bad state (requiring restart of VS Code)~
- ~Status bar had a message
running tests
(this never went away)~ - ~Debugger bar appeared on the top (clicking stop did nothing)~
- ~Debug adapter failed with usual message
Debug adapter failed unexpectedly
~
- ~Status bar had a message
- ~Deleting
Experimental Debugger
configuration settings fromlaunch.json
fixed a lot of the issues~
Todo:
- Improve error handling and logging (diagnosing)
- User should never have to reload VS Code
~* Recover from a state where debugger has a message
running tests
~
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Is there a jest config that will fail tests on console.warn?
You can set the environment variable CI=true before running jest which will cause it to fail tests on warnings in addition to errors....
Read more >Catch warnings in Jest tests | Ben Ilegbodu
I exclusively use Jest for writing JavaScript unit tests, and unfortunately it doesn't yet have a configuration for failing on console.warn ...
Read more >"configuration not public" on local test->test dependency if the ...
Prioritize inter-project resolution over Ivy cache. Here's another idea: Display a warning saying test->test won't work if publishMavenStyle is ...
Read more >Troubleshooting guide for testing with the Performance SDK
This article provides troubleshooting information for issues that you might encounter during single-user or multi-user testing that uses the ...
Read more >Diagnostics option | ts-jest - Huafu
warnOnly : If specified and true , diagnostics will be reported but won't stop ... test files ends with .spec.ts or .test.ts ,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@DonJayamanne I tweaked the title to try and reflect what I think the issue is. Basically this is if
"python.unitTest.unittestEnabled": true
but"python.unitTest.unittestArgs"
is unset?I’m going to close the issue, because even if the configuration is done manually, and only the value of “unittestEnabled” is updated, when trying to run the tests, it shows this: In other words, it shows you that the configuration is wrong or incomplete and suggests you do it again.