Safari test run breaks in Sauce Lab due to missing W3C WebDriver support
See original GitHub issueFull background: https://github.com/sinonjs/sinon/issues/2372.
Basically, Safari tests breaks with v12 and up. This needs to be fixed in min-wd
(mantoni/min-webdriver#31).
Issue Analytics
- State:
- Created 2 years ago
- Comments:17 (15 by maintainers)
Top Results From Across the Web
Common Error Messages | Sauce Labs Documentation
It indicates that the OnDemand portion of the Sauce Labs service lost its connection with the Virtual Machine running a test.
Read more >Sauce Labs FAQs | Comparably
Find answers to frequently asked questions on Sauce Labs's FAQ page on Comparably. ... UnsupportedCommandException Error When Running Chrome with W3C ...
Read more >The Latest Changes To Selenium WebDriver 4.0 ... - Ultimate QA
Selenium 4.0 is released with tons of changes to .NET bindings. What are those changes and how can you prevent them from breaking...
Read more >appium/appium - Gitter
Ensure to only use valid W3C WebDriver capabilities (see ... If you run your tests on a remote vendor, like Sauce Labs or...
Read more >WebdriverIO + Appium + Sauce Labs = Success? - Live Stream
Stream starts at 00:03:15Last week there was a request to set up WebdriverIO with Appium + Sauce Labs to test a Web App....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I figured it out for this project and have a fix in https://github.com/mantoni/mochify.js/pull/244 (spoiler: there’s a very subtle bug in the geckodriver).
I’m happy to provide assistance for anyone who is willing to help. I’m sorry for the lack of documentation. A good way to start is to read through the initial “Mochify Rewrite” issue: https://github.com/mantoni/mochify.js/issues/229
Issues for the rewite can be found here: https://github.com/mantoni/mochify.js/milestone/1
Sounds great! I’ll wait for the PR. Thank you for being patient and helpful about all of it.