-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Unittest args doesn't support -t flag #5721
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
Comments
I digged into the code and I think the fix is relatively easy, actually -t is a "knowOptions" for unittests, however: Here, when discovery is triggered: There is a third optional argument See https://docs.python.org/2/library/unittest.html#unittest.TestLoader.discover and https://docs.python.org/3/library/unittest.html#unittest.TestLoader.discover I can provide a PR with the necessary changes that should be limited to |
Thanks for the investigation, please do provide a PR. |
@Fraggle any issue making this more difficult than previously anticipated? |
We fixed a lot of related code, is this now fixed in the latest version of the extension? |
Hi! From my understanding of the extension right now the Lets move to this other issue to consolidate the discussion, thanks! |
This issue: #2162 was closed is was considered a duplicate of another issue.
However, I still can't make vs code discover our tests right now as the "-t" flag is still not supported as a python.testing.unittestArgs.
I confirm that using a terminal to execute the same discovery command but with the -t flag specified works when it doesn't without.
My request is to re-open the issue and add support for -t flag.
The text was updated successfully, but these errors were encountered: