-
Notifications
You must be signed in to change notification settings - Fork 28k
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
Profile/metadata feedback on testing #218102
Comments
I realized I never followed up on #144169 (comment), apologies.
The filtering is possible through use of the
Yea, currently users can pick the default profile used when they hit the button, but a non-default option will involve extra steps. However I did make a change in more recent versions such that the "run" button always works regardless of whether the default profile is applicable or not (we'll fall back to whatever profile does match it.) Not sure if that solves your use case, but I'd like to try and make profiles work for you. Maybe we finally do need to add code lenses 😛 #133338
Related, you may be interested in the ![]() |
However, restart doesn't work great - because it seems to end the test run, then start a new debug session that is not tied to a test run (so you don't get the results recorded). It's not clear to me if your fix here will solve that, but I wonder if there are going to have issues with test runs where VS Code doesn't have all of the related data. We discussed this before in #144169 (comment) about "Test: Rerun Last Run" not working because of this. If we let VS Code handle restarting test runs by just calling
runTests
, I think any context that we weren't able to capture in theTestRun
won't come back to us, and we'll start a test run with some parameters missing.Originally posted by @DanTup in #214486 (comment)
The text was updated successfully, but these errors were encountered: