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 creating a test script, it's a common pattern to use the devtools inspector to view the webpage under test to find elements in the page that we want to work with. It's also useful for many other reasons, especially when bugs within the website under test are affecting the test.
At the moment there isn't a convenient way to have the devtools window open while the test is running [in headful mode]. It usually requires adding sleep or page.waitForTimeout in the test script to allow time to open devtools and inspect the website under test.
It would be good if we can improve the DX so that the devtools window opens when the test starts and keep it open throughout the test run.
Suggested Solution (optional)
Provide a configuration (env var) to have the devtools window open when running in headlful mode only.
Honour 'debugger' statements and pause the execution automatically without having to place sleep or page.waitForTimeout.
Already existing or connected issues / PRs (optional)
No response
The text was updated successfully, but these errors were encountered:
Feature Description
When creating a test script, it's a common pattern to use the devtools inspector to view the webpage under test to find elements in the page that we want to work with. It's also useful for many other reasons, especially when bugs within the website under test are affecting the test.
At the moment there isn't a convenient way to have the devtools window open while the test is running [in headful mode]. It usually requires adding
sleep
orpage.waitForTimeout
in the test script to allow time to open devtools and inspect the website under test.It would be good if we can improve the DX so that the devtools window opens when the test starts and keep it open throughout the test run.
Suggested Solution (optional)
sleep
orpage.waitForTimeout
.Already existing or connected issues / PRs (optional)
No response
The text was updated successfully, but these errors were encountered: