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
With parametrized tests, the results are hard to read in the "running tests for ..." right side window of test results.
For non-parametrized tests, the test name is listed.
For parametrized tests, the parameters are listed without the test name.
I think it would be easier to read if it was "test_name[param_value]", similar to how pytest -v shows the results.
Steps to reproduce:
Run a test with parametrizations.
Here's a small example:
I'm attaching a screen shot of the output to demo the issue.
In this example I think "test_b[1]" and "test_b[2]" would be easier to read than "[1]" and "[2]".
The problem is more pronounced with a parametrized fixture.
Example:
Type: Bug
Behaviour
With parametrized tests, the results are hard to read in the "running tests for ..." right side window of test results.
For non-parametrized tests, the test name is listed.
For parametrized tests, the parameters are listed without the test name.
I think it would be easier to read if it was "test_name[param_value]", similar to how
pytest -v
shows the results.Steps to reproduce:
Run a test with parametrizations.
Here's a small example:
I'm attaching a screen shot of the output to demo the issue.
In this example I think "test_b[1]" and "test_b[2]" would be easier to read than "[1]" and "[2]".
The problem is more pronounced with a parametrized fixture.
Example:
Results in:
Diagnostic data
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)Extension version: 2024.18.0
VS Code version: Code 1.95.1 (65edc4939843c90c34d61f4ce11704f09d3e5cb6, 2024-10-31T05:14:54.222Z)
OS version: Windows_NT x64 10.0.22631
Modes:
The text was updated successfully, but these errors were encountered: