Repository navigation
Problem to recognize tests with @pytest.mark.parametrize decorator #785
Description
Hello guys.
I've been facing some problems here when trying to debug tests that is decorated with parametrize.
VsCode can't recognize these tests with parametrize from pytest.
my .vscode/settings.json:
{
"python.testing.pytestArgs": [
"tests"
],
"python.testing.unittestEnabled": false,
"python.testing.pytestEnabled": true
}
My VsCode version: 1.103.1
Does anyone know how to resolve this problem?
Activity
eleanorjboyd commentedon Aug 22, 2025
What problem are you facing?
roschel commentedon Aug 22, 2025
The problem is that the run/debug button from vscode doesn't appear when the test is decorated with
@pytest.mark.parametrize.According with the picture I attached, the first test, which is decorated, doesn't have the run/debug enabled. While the second test without the decorator has the run/debug button enabled.
Why this happen in vscode?
roschel commentedon Aug 27, 2025
Hello?
eleanorjboyd commentedon Aug 29, 2025
can you run
python -m pytest --collect-only -vI think that is the collect in verbose mode so I can look at the test ids as those determine how the tests are found and loaded into the UIroschel commentedon Sep 1, 2025
Sure, here it's the output
github-actions commentedon Oct 2, 2025
Hey Eleanor Boyd (@eleanorjboyd), this issue might need further attention.
João Roschel (@roschel), you can help us out by closing this issue if the problem no longer exists, or adding more information.
roschel commentedon Oct 2, 2025
Hello? Eleanor Boyd (@eleanorjboyd)
roschel commentedon Oct 14, 2025
Hello?
github-actions commentedon Nov 14, 2025
Hey Eleanor Boyd (@eleanorjboyd), this issue might need further attention.
João Roschel (@roschel), you can help us out by closing this issue if the problem no longer exists, or adding more information.
github-actions commentedon Dec 15, 2025
Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.
Happy Coding!
github-actions commentedon Jan 15, 2026
Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.
Happy Coding!
roschel commentedon Feb 5, 2026
Well, I think that's how microsoft support works. They don't even answer your questions. Very nice!