Debugging: Run to Completion and Restart #140580
Comments
|
@connor4312 what do you think? |
|
The test case would be partially covered by #134941. Though we don't have any plan/feature right now to "disable breakpoints for the current test run and continue". I would probably backlog-candidate this feature request. |
|
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
|
This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Among the Debug actions in the Debug Toolbar (
Pause/Continue,Step Over,Step Into,Step Out,Restart,Stop), it would be useful to have a button that is similar toRestart, but will continue the code to its exit (error or otherwise), then start it again.This would be very useful when, for example, debugging an E2E test from the Python Test Extension which has a fixture that requires cleanup. Right now, if you were to Restart an test in progress, it would skip the cleanup/teardown steps of that fixture. A
Finish & Restartbutton would allow for teardown to occur before restarting the test. Of course, this would make code changes faster to debug in these scenarios.Optionally, I think it would make sense to allow this feature to skip breakpoints (or a certain level of breakpoints) until the current run exits.
Apologies if this has already been requested. I did some searching, but this isn't an easy concept to specify in search.
The text was updated successfully, but these errors were encountered: