Skip to content

ci: run integration tests against local selenium/standalone-chrome#2232

Open
Artur- wants to merge 1 commit into
mainfrom
no-saucelabs
Open

ci: run integration tests against local selenium/standalone-chrome#2232
Artur- wants to merge 1 commit into
mainfrom
no-saucelabs

Conversation

@Artur-
Copy link
Copy Markdown
Member

@Artur- Artur- commented May 7, 2026

Replace SauceLabs cloud grid + Sauce Connect tunnel with a selenium/standalone-chrome service container on the GitHub Actions runner. Tests reuse the existing remote-driver code path, just pointed at localhost:4444 instead of the Sauce hub.

Drop Safari and Windows 10 platform forcing from the integration test browser configurations so capabilities match what the Linux container can serve.

The SauceLabsIntegration public API and routing in BrowserExtension / ParallelTest are unchanged — users who set SAUCE_USERNAME / SAUCE_ACCESS_KEY externally still get the Sauce path.

Replace SauceLabs cloud grid + Sauce Connect tunnel with a
selenium/standalone-chrome service container on the GitHub Actions
runner. Tests reuse the existing remote-driver code path, just pointed
at localhost:4444 instead of the Sauce hub.

Drop Safari and Windows 10 platform forcing from the integration test
browser configurations so capabilities match what the Linux container
can serve.

The SauceLabsIntegration public API and routing in BrowserExtension /
ParallelTest are unchanged — users who set SAUCE_USERNAME /
SAUCE_ACCESS_KEY externally still get the Sauce path.
@mshabarov mshabarov requested review from mshabarov and platosha May 11, 2026 11:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant