2

I have Jenkins working with OS X slave nodes using selenium over ssh.

I've successfully run the command below to ensure that it is configured correctly.

/usr/bin/safaridriver --enable

When I run a build, I can see the tests starting to run and safaridriver runs, but immediately exits with an error code. At this stage the tests hang.

If I manually run safaridriver with the exact same commandline, then the tests start.

In essense, /usr/bin/safaridriver errors out when run over ssh, but doesn't if it is run locally. The same is true no matter what user you run it as.

I'm using High Sierra, Safari 11.1.2 and Selenium 3.14.

Anyone run into this problem?

gil
  • 1,318
  • 12
  • 19
Joe Warren-Meeks
  • 21
  • 2

1 Answers1

0

You can use Automator to create an app to start safaridriver, like this: Unable to run tests against Safari 11 remotely (ssh, CI)

Duy Banh
  • 51
  • 2