Skip to content

Reconfiguring tests doesn't update Testing panel #21131

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

Closed
Yoyokrazy opened this issue Apr 25, 2023 · 3 comments
Closed

Reconfiguring tests doesn't update Testing panel #21131

Yoyokrazy opened this issue Apr 25, 2023 · 3 comments
Assignees
Labels
area-testing bug Issue identified by VS Code Team member as probable bug

Comments

@Yoyokrazy
Copy link

Testing #21092

When reconfiguring tests from pytest -> unittest, the test panel doesn't automatically refresh. The refresh test button also just leaves the pytest header remaining at the top of the tree, rather than updating to the unittest filtered tests.

image

Reloading updates the testing panel to the correct output.

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

eleanorjboyd commented Apr 26, 2023

Seeing a similar result right now on our current testing panel. I included a recording of what happens on insiders without the rewrite turned with the same steps. Therefore this is a bug but not a regression in functionality from the current testing experience.

switch_test_types_release_v.mov

@github-actions github-actions bot added the info-needed Issue requires more information from poster label Apr 26, 2023
@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 Apr 26, 2023
@eleanorjboyd
Copy link
Member

Looking for community feedback here, do people often switch between the testing infrastructures and run into this problem?

@eleanorjboyd
Copy link
Member

use case too small and would require too much work to be a priority

@eleanorjboyd eleanorjboyd closed this as not planned Won't fix, can't repro, duplicate, stale Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-testing bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

2 participants