-
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
Error: Test result not found when using parameterized fixtures #17079
Comments
I think I have found the issue, it is the forward slash character in the params |
Can you verify using this VSIX: https://github.com/microsoft/vscode-python/suites/3584266029/artifacts/86250061 ? |
I am experiencing a similar issue in all my tests, being them parametrized with fixtures or not. I have my repo divided in multiple workspaces, so I am not sure this issue might be related to that. |
@jzazo Can you file a separate bug and provide repro details? |
I have created the following issue with repro details: #17343 |
@karthiknadig I am still experiencing this issue. I don't have any slashed in my params. My last update is apparently (but not sure how to really check it): 04/11/2021, 19:40:15. Is it enough to have the fix to this problem? EDITSorry about that, this was just a VSCode version problem |
Environment data
python.languageServer
setting: Pylance[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (
python.languageServer: 'Microsoft'
), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]Expected behaviour
I'm using a parameterized fixture for my package, which runs tests against a group of valid configuration files
Actual behaviour
All of my tests are passing, however, for each parameterized test I get something like:
Test result not found for: ./tests/test_postprocessing.py::TestPostprocessing::test_input_type[experiments/config.yml]
If I remove the parameterization here then the testing sidebar finds all of the test results just fine and confirms they all succeeded. The test log output also has no issues and says everything passed.
Steps to reproduce:
I think writing some simple pytests with these files should reproduce this and also use the same characters in the params in case it's a special character issue.
The text was updated successfully, but these errors were encountered: