Skip to content

Support --pause-after-load in visible browsers #294

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
nex3 opened this issue Jul 22, 2015 · 2 comments
Closed

Support --pause-after-load in visible browsers #294

nex3 opened this issue Jul 22, 2015 · 2 comments
Labels
type-enhancement A request for a change that isn't a bug
Milestone

Comments

@nex3
Copy link
Member

nex3 commented Jul 22, 2015

The simplest way to debug browsers is using the dev inspector, but by default the test runner doesn't make that easy, since browsers start and complete quickly and without user input. We should add a flag (e.g. --pause-after-load) that pauses the test runner after a browser has loaded a test suite to allow users to access the dev console, set breakpoints, and so forth. They should then be able to resume the test either via the command line or by clicking a link on the host page.

Obviously this will only work for browsers with visible windows. #295 and #296 track support for debugging headless browsers.

@nex3 nex3 added the type-enhancement A request for a change that isn't a bug label Jul 22, 2015
@nex3 nex3 added this to the 0.12.4 milestone Jul 22, 2015
@nex3 nex3 changed the title Support dev-inspector based debugging in browsers Support --pause-after-load in visible browsers Jul 22, 2015
nex3 added a commit that referenced this issue Jul 23, 2015
Currently this only support windowed browsers and the runner can only be
unpaused from the command line.

See #294

[email protected]

Review URL: https://codereview.chromium.org//1248073003 .
@nex3 nex3 closed this as completed in 8fcfc7a Jul 30, 2015
@michalpie
Copy link

When I run tests on Windows using the newest (1.16) release with

pub run test -p dartium --pause-after-load

then the test is paused, but the 'Play' button is not shown. It seems there is no way to start the tests.

@zoechi
Copy link

zoechi commented Apr 28, 2016

@michalpie I think you should create a new issue for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-enhancement A request for a change that isn't a bug
Projects
None yet
Development

No branches or pull requests

3 participants