This repository was archived by the owner on Jul 29, 2024. It is now read-only.
fix(runner): prefer sauce to hosted driver when sauceKey is present #1115
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sauce Connect sets up a local Selenium relay at localhost:4445 by
default. Allow users to adjust the
seleniumAddress
to point at thissecure relay instead of the default
ondemand.saucelabs.com
host whilestill using the
sauce
driver provider.Previously, runner would load the
remote
driver provider ifseleniumAddress
was configured, even if Sauce credentials were alsoconfigured.
For reasons not clear to me, on Travis VMs, the Sauce Connect relay is 10x more reliable than
ondemand.saucelabs.com
. It might be worth testing whether this helps with protractor's test suite oddities (#1051 and #1052)