-
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
Is it possible to connect pytest assert failures to problems and code views? #120
Comments
Does sound like a good suggestion, however what's interesting is that this hasn't been up voted by anyone. I'll check this feature with my colleagues and get back to you. There could be other edge cases that need to be considered, e.g. what if the unit tests pass, we'll then need to ensure the problems disappear. |
@brettcannon @qubitron |
This is a great feature, but is there a way to disable the red underlines for failing tests? I think of the red underlines as indicating linting/syntax errors, so I find it a bit confusing that they're overloaded to indicate test failures. Thanks for working on this though! |
Please create a separate issue and we can go from there. |
From @hendrics on May 21, 2017 20:15
Hi. I was wondering if there's an option to integrate assert failures and problem/code view.
I managed to hack it together using
problemMatchers
for tasks.See the details example here
https://github.com/hendrics/python-vscode-pytest-example
Also i am looking for an ability to add links to the Output view to jump to the code.
There are open issues on the vscode to address it via matchers.
So overall copy pasting the
tasks.json
around is not scalable and i am wonderingif there's scope to add it to this extension unless it is already implemented.
Environment data
VS Code version: Version 1.12.2 (1.12.2)
Python Extension version: Version 0.6.4 (4 May 2017)
Python Version: 2.7.11
OS and version: macOS El Capitan
Copied from original issue: DonJayamanne/pythonVSCode#973
The text was updated successfully, but these errors were encountered: