You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello!
I am the maintainer of testing for vscode-python and have been investigating: microsoft/vscode-python#23933. I have some questions in regards to how I can support pytest-mypy. This discussion is similar to the one I started on the pytest-ruff repo here: businho/pytest-ruff#32.
I explained a bit in the attached issue but what I think the best fix is would be including an extra "mypy" test node nested under each file node on the test explorer. (one side question I have is if there should be two nodes? The mypyFileItem and the mypyStatusItem?) We run tests based on their test-ids, so this would mean the mypy test would have a test-id that would be passed. Also it would fix the issue where no tests show up, this is just a side effect of the mypy node impacting the discovery process. Looking for a bit of advice as there is a piece of implementation.
What happens is while building the test tree to then display is I cycle through all the session.items see code. I am not seeing the mypy node- is this added after or should I expect it during run? I see if I run python -m pytest --mypy --collect-only from the terminal I do get 3 items:
Hello!
I am the maintainer of testing for vscode-python and have been investigating: microsoft/vscode-python#23933. I have some questions in regards to how I can support pytest-mypy. This discussion is similar to the one I started on the pytest-ruff repo here: businho/pytest-ruff#32.
I explained a bit in the attached issue but what I think the best fix is would be including an extra "mypy" test node nested under each file node on the test explorer. (one side question I have is if there should be two nodes? The mypyFileItem and the mypyStatusItem?) We run tests based on their test-ids, so this would mean the mypy test would have a test-id that would be passed. Also it would fix the issue where no tests show up, this is just a side effect of the mypy node impacting the discovery process. Looking for a bit of advice as there is a piece of implementation.
What happens is while building the test tree to then display is I cycle through all the
session.items
see code. I am not seeing the mypy node- is this added after or should I expect it during run? I see if I runpython -m pytest --mypy --collect-only
from the terminal I do get 3 items:so during collect it does exist but im not sure how I can see / access it from my plugin.
I appreciate any advice on how to support this. I have a few more questions but wanted to get the ball rolling with this initial one. Thanks
The text was updated successfully, but these errors were encountered: