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
When debugging, I would like to be able to run the tests, or an individual test, over again. For example, suppose I have a failure I want to debug. I run the test with the --pause-at-load feature, turn on stopping at exceptions, ignoring caught exceptions, and any other options I need. It stops, I see that something has the wrong value. Now I want to set a breakpoint a couple of steps earlier to see where that's coming from. Without the test package I would just re-load the page, but that kills the test. So I write down on a post-it where the breakpoint needs to be, kill the test, run it again with that option, set my options again, find the spot for the breakpoint, set it, and run the test.
With the SDK test runner, when I have failures I can run it in a debug mode where the test runs all the way through but the browser doesn't it. I get a report of the failures on the page, and I can open development tools, set my options, and click on any individual report to run a specific test over again. Or I can reload the page and re-run everything.
The text was updated successfully, but these errors were encountered:
When the browser is paused at a breakpoint, the runner will now open a
command-line console with a "restart" command that will restart the
current test.
This currently has no tests, due to dart-lang/sdk#25369 and the lack of
a programmatic API for interacting with Observatory. I've tested it
reasonably thoroughly by hand, but it's more likely than the average
feature to have lurking bugs.
Closes#335[email protected]
Review URL: https://codereview.chromium.org//1561073003 .
When debugging, I would like to be able to run the tests, or an individual test, over again. For example, suppose I have a failure I want to debug. I run the test with the --pause-at-load feature, turn on stopping at exceptions, ignoring caught exceptions, and any other options I need. It stops, I see that something has the wrong value. Now I want to set a breakpoint a couple of steps earlier to see where that's coming from. Without the test package I would just re-load the page, but that kills the test. So I write down on a post-it where the breakpoint needs to be, kill the test, run it again with that option, set my options again, find the spot for the breakpoint, set it, and run the test.
With the SDK test runner, when I have failures I can run it in a debug mode where the test runs all the way through but the browser doesn't it. I get a report of the failures on the page, and I can open development tools, set my options, and click on any individual report to run a specific test over again. Or I can reload the page and re-run everything.
The text was updated successfully, but these errors were encountered: