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
Attempting to get the current timeout values is failing using seleniumServer. I'm running a Nightwatch test with the command 'this.timeouts((result) => { console.log('timeouts:', result) })'. In the verbose output I see this ...
kretschmannj
changed the title
The 'get' timeouts command is failing in Firefox with Selenium Server
The 'get' timeouts command is failing when using Selenium Server
Oct 16, 2020
With the lastest version, both http://localhost:4444/wd/hub/session/<session-id>/timeouts and http://localhost:4444/session/2407738ef8bfb7a0a74dcbe6f962858c/<session-id>/timeouts in the Standalone mode.
Those commands are failing for Grid 3.141.59, but if you try the new Grid 4 (currently at Alpha 7 and soon Beta 1), they will work, as pointed out above.
Closing this issue as it is working on the new Grid 4.
🐛 Bug Report
Attempting to get the current timeout values is failing using seleniumServer. I'm running a Nightwatch test with the command 'this.timeouts((result) => { console.log('timeouts:', result) })'. In the verbose output I see this ...
I only have this issue when I use the standalone selenium server ...
I have no such issue when I use webdriver/geckodriver ...
Environment
OS: Windows 10
Browser: Chrome or Firefox (fails in both)
Browser version: Chrome 85 / Firefox 81.0.2
Browser Driver version: ChromeDriver 85.0.4183.87 / GeckoDriver 0.27.0
Nightwatch version: 1.4.2
The text was updated successfully, but these errors were encountered: