Resolving the WebDriverException with safaridriver on macOS

Описание: Discover how to fix the `WebDriverException` caused by `safaridriver` on macOS, ensuring successful remote testing with Robot Framework.
---
This video is based on the question https://stackoverflow.com/q/65123672/ asked by the user 'Victor Vogt' ( https://stackoverflow.com/u/14755098/ ) and on the answer https://stackoverflow.com/a/65249041/ provided by the user 'Victor Vogt' ( https://stackoverflow.com/u/14755098/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: RobotFramework - WebDriverException: Message: Service /usr/bin/safaridriver unexpectedly exited. Status code was: 1

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Troubleshooting WebDriverException with safaridriver on macOS

When running automated tests using Robot Framework on macOS, you may encounter an error that stops your tests in their tracks. One particularly bothersome issue is the WebDriverException with the message stating: "Service /usr/bin/safaridriver unexpectedly exited. Status code was: 1". This can be a significant roadblock, especially if your tests work smoothly on browsers like Firefox and Chrome. In this guide, we’ll explore what causes this issue and how you can resolve it effectively.

Understanding the Problem

The error message indicates that the safaridriver needed to run Safari tests has unexpectedly terminated. Upon further inspection in the console, you might come across the following errors:

[[See Video to Reveal this Text or Code Snippet]]

This typically points to an authorization issue where the safaridriver cannot launch due to insufficient privileges. Although your other browser tests work perfectly, Safari does come with its specific security measures that can complicate automated test launches.

Current Setup

For context, let’s look at the setup used when encountering this issue:

Python: 2.7.16

Selenium: 3.141.0

Robot Framework: 3.0.2

macOS: Mojave 10.14.6

Safari: 14.0.1 (safaridriver bundled)

Exploring the Solution

Reviewing Authorization Rights

The main culprit in this scenario is the user account that launches the Tomcat server. Often, services that require GUI interactions (like a web browser) need to be run by a user account that has the necessary rights to display interfaces. The good news is that resolving this issue is straightforward. Follow these steps:

Check the User Account:

Ensure that the Tomcat server is started by a user that has display rights. If it’s currently running under a system or admin user without GUI access, you won't be able to launch safaridriver successfully.

Restarting the Tomcat Server:

Stop the existing Tomcat server session:

[[See Video to Reveal this Text or Code Snippet]]

Start it again using a regular user account that is logged into macOS, instead of a system account:

[[See Video to Reveal this Text or Code Snippet]]

Allowing Remote Automation

In addition to the user account, ensure that remote automation is permitted in Safari. If you haven’t already done this, execute the following command:

[[See Video to Reveal this Text or Code Snippet]]

This enables the necessary permissions for remote automation that Safari requires to run tests.

Conclusion

If you’re dealing with the WebDriverException due to safaridriver while running tests on Safari, remember that the problem usually lies with the user account and its privileges. By ensuring that your Tomcat server is launched by a user with proper display rights and confirming that the necessary automation settings are in place for Safari, you'll enjoy seamless testing on all browsers.

Final Thoughts

Navigating the complexities of macOS testing can be tricky, especially with the unique quirks of Safari. If you run into further challenges, consider checking community forums, as many users share similar experiences – and solutions. Implementing these steps should streamline your testing process, making your tests as flawless as they are on Chrome and Firefox.

Happy Testing!