Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Don't use Sauce Connect's Selenium Relay #1151

Open
jason0x43 opened this issue May 13, 2020 · 0 comments
Open

Don't use Sauce Connect's Selenium Relay #1151

jason0x43 opened this issue May 13, 2020 · 0 comments
Labels
domain-tunnels Related to Intern's webdriver tunnels (formerly Dig Dug) effort-medium This may take a couple of days enhancement A new or improved feature priority-medium This should get done, but it's not a high priority

Comments

@jason0x43
Copy link
Member

Intern 4.x and 5-pre use Sauce Connect's Selenium Relay when running tests on Sauce. Sauce Connect is setup to listen on the standard Selenium port 4444 with the -P option, and Intern treats it like a local Selenium server. Sauce doesn't recommend this, and the functionality will be removed in a future release.

Instead, Intern should use Sauce over HTTPS, similarly to how BrowserStackTunnel works.
@jason0x43 jason0x43 added enhancement A new or improved feature effort-medium This may take a couple of days domain-tunnels Related to Intern's webdriver tunnels (formerly Dig Dug) priority-medium This should get done, but it's not a high priority labels May 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
domain-tunnels Related to Intern's webdriver tunnels (formerly Dig Dug) effort-medium This may take a couple of days enhancement A new or improved feature priority-medium This should get done, but it's not a high priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jason0x43