forked from DonJayamanne/pythonVSCode
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Cannot run unittests discovered with --pattern flag #8465
Labels
Milestone
Comments
eirki
added
triage-needed
Needs assignment to the proper sub-team
bug
Issue identified by VS Code Team member as probable bug
labels
Nov 8, 2019
Thanks for the bug report! We just wanted to acknowledge that we got the report, triaged it, and have determined it is a bug. |
3 tasks
ericsnowcurrently
modified the milestones:
2019 November Sprint 1,
2019 November Sprint 2
Nov 20, 2019
validated |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Environment data
Expected behaviour
Python: Run all tests
should run tests that have been discovered.Actual behaviour
Tests are discovered, but when I select
Run all tests
, no tests run.Steps to reproduce:
Very basic (but non-standard) file structure:
Contents of
settings.json
:Contents of
file.py
Logs
Output for
Python
in theOutput
panel(Notice the argument to
visualstudio_py_testlauncher.py
is--up=test*.py
. This is the default pattern, not"*.py"
as specified in thesettings.json
)Output from
Python Test Log
However, when I change
"--pattern"
to"-p"
and try to re-run the tests, it works:Python
Log:(Now
visualstudio_py_testlauncher.py
get's the correct argument,--up=*.py
, )Python Test
Log:I think I've found the source of the bug in this line, which tries to parse the argument
'-pattern'
, and not'--pattern'
. I changed it manually in the compiledextension.js
file and that seemed to fix it. I'd be happy to try to and fix it in the source and submit a PR, but I am not very TypeScript proficient.The text was updated successfully, but these errors were encountered: