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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: