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
{{ message }}
This repository has been archived by the owner on Dec 18, 2019. It is now read-only.
In theory you should be able to call brower.debug() to manually inspect the browser state continue when you are ready by pressing enter at the console.
This works fine using the async api in a standalone js file, but calling debug in a test runner will timeout and fail the test without waiting for user to press enter at the console.
I assumed this was wdio-sync causing the timeout but rewrote the test in async style without sync option and still getting timeout. Seems to be the jasmine test runner is responsible for the timeout. I'm not sure if you have any suggestions, perhaps a clever way for wdio-sync to "ping" jasmine so to prevent it from timing out, but I'll close this issue here and reopen it on https://github.com/webdriverio/wdio-jasmine-framework
In theory you should be able to call brower.debug() to manually inspect the browser state continue when you are ready by pressing enter at the console.
This works fine using the async api in a standalone js file, but calling debug in a test runner will timeout and fail the test without waiting for user to press enter at the console.
http://webdriver.io/api/utility/debug.html
Is there a way to prevent this command from timing out?
The text was updated successfully, but these errors were encountered: