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
After navigating to URL, why don't the browsers let go? My tests start on Saucelabs (QUnit tests) and the browsers sit there doing nothing until the 3 minute (no activity) timeout is reached and then they finally give up. What am I doing wrong? I am expecting that immediately after the browser navigates to the initial URL, the test should end successfully right there BUT this is not what I see.
After navigating to URL, why don't the browsers let go? My tests start on Saucelabs (QUnit tests) and the browsers sit there doing nothing until the 3 minute (no activity) timeout is reached and then they finally give up. What am I doing wrong? I am expecting that immediately after the browser navigates to the initial URL, the test should end successfully right there BUT this is not what I see.
I configured my Gruntfile.js like this:
And the error I get looks like this, complaining about a 'length' parameter that I presume to be the 180 second timeout value?
The text was updated successfully, but these errors were encountered: