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
I have some skipped tests, and I'd like to see those in the tree view. However files are closed by default.
This causes me to manually open all directories and all nested files, then all classes within those classes to see the concrete class tests.
Some feature requests have already been requested however were closed and we can no longer upvote.
It is nearly impossible to find skipped tests in deeply nested testing directory structure without a "expand all' feature. Ex: I have to go 4 layers deep to find the skipped tests, this becomes very tedious in 1000+ testing structures.
The text was updated successfully, but these errors were encountered:
Thank you for the suggestion! We have marked this issue as "needs decision" to make sure we have a conversation about your idea. We plan to leave this feature request open for at least a month to see how many 👍 votes the opening comment gets to help us make our decision.
@connor4312, I see the linked vscode issue was closed because it wasn't going to get addressed in the near future. Any thoughts on this now, would it be something core would address now? I would be interested in the difficulty of implementing it verse the functionality gain. Thanks
I have some skipped tests, and I'd like to see those in the tree view. However files are closed by default.
This causes me to manually open all directories and all nested files, then all classes within those classes to see the concrete class tests.
Some feature requests have already been requested however were closed and we can no longer upvote.
microsoft/vscode#88682
#11362
It is nearly impossible to find skipped tests in deeply nested testing directory structure without a "expand all' feature. Ex: I have to go 4 layers deep to find the skipped tests, this becomes very tedious in 1000+ testing structures.
The text was updated successfully, but these errors were encountered: