ci: run integration tests against local selenium/standalone-chrome#2232
Open
Artur- wants to merge 5 commits into
Open
ci: run integration tests against local selenium/standalone-chrome#2232Artur- wants to merge 5 commits into
Artur- wants to merge 5 commits into
Conversation
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.
Test Results 190 files 190 suites 15m 23s ⏱️ Results for commit e5f07a6. ♻️ This comment has been updated with latest results. |
…n local grid Gate the SeleniumJupiter PageObject example tests on whether a remote grid is configured (hubHostname or Sauce Labs) instead of on Sauce Labs specifically: - SeleniumLocalPageObjectIT (local ChromeDriver via WebDriverManager) is disabled whenever a remote grid is configured, so it no longer tries to launch a non-existent local Chrome on the CI runner. - SeleniumHubPageObjectIT now runs against whichever remote grid is configured; AbstractSeleniumSauceTB9Test derives the hub URL and capabilities from Sauce Labs when configured, otherwise from the hubHostname parameter (the selenium/standalone-chrome container in CI). Also fix a latent race in MoveTargetOutOfBoundsIT.scrollIntoView...: the grid-like container applies its sticky-tbody compensation transform on a requestAnimationFrame, so the target reaches its final position one frame after scrollIntoView returns. Poll for the settled position instead of reading it synchronously, which raced the rAF on fast local drivers (Sauce Labs' command latency previously masked this).
The JUnit 5 copy of ElementScreenCompareIT is already @disabled("Viewport resize does not work"); its JUnit 4 twin was missing the equivalent @ignore, so it ran against the local selenium/standalone-chrome grid and failed: the reference screenshots only cover Windows/Mac browsers, so on Linux Chrome no reference matches and the comparison fails. Mirror the twin's annotation.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
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.