Skip to content
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

Parametrized tests should be under their own node #21340

Closed
karthiknadig opened this issue May 30, 2023 · 2 comments · Fixed by #21368
Closed

Parametrized tests should be under their own node #21340

karthiknadig opened this issue May 30, 2023 · 2 comments · Fixed by #21368
Assignees
Labels
area-testing bug Issue identified by VS Code Team member as probable bug

Comments

@karthiknadig
Copy link
Member

Testing #21092

image

Expected layout:

test_fibb
 |-test_fibb
 |- test_new_test
 |- test_large_range
     |- 0
     |- 1
     .
     .
     |- 9999

@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label May 30, 2023
@eleanorjboyd
Copy link
Member

The image is not rendering for me- could you try uploading it again? This is what I am seeing on my UI which I thought was the expected layout:

image

@eleanorjboyd eleanorjboyd added the info-needed Issue requires more information from poster label May 30, 2023
@eleanorjboyd
Copy link
Member

The structure is currently missing a node for the parameterize test class which the parameterize tests will sit under.

@eleanorjboyd eleanorjboyd added bug Issue identified by VS Code Team member as probable bug area-testing and removed info-needed Issue requires more information from poster triage-needed Needs assignment to the proper sub-team labels Jun 5, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 9, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-testing bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants