[🐛 Bug]: Running tests in parallel in docker causing tests to choose the wrong open window

[jonn-set]

Description

I am running Selenium tests in parallel inside a Docker container (standalone-chrome) using the Surefire plugin. 80-90% of my tests fail and the screenshots captured in the After hook seem to indicate that a different test was running, like its querying a customer that is not part of thread the test is running in, etc., extremely difficult to put a finger on it and say what's wrong. I also see a lot of org.openqa.selenium.StaleElementReferenceException: stale element reference: stale element not found in the current frame. Which seems to indicate the test is trying to access the wrong open browser window.

I also use Spring and am using SimpleThreadScope() to create a 'thread' scope, the WebDriver & ScenarioContext are all marked as @Scope(scopeName = "thread") so I believe the configuration is correct as they all seem to work as expected in Windows on Edge, however when I run this in docker, it does not work.

My Project code base is very big and cant be shared on the forum, but I will try to create a separate project and share the link here, in the meantime if anyone notice anything obvious I am doing wrong, can they comment and let me know please.

Reproducible Code

These are the options I pass into the RemoteWebDriver Object when I build it:

--enable-automation
--disable-extensions
--disable-client-side-phishing-detection
--no-default-browser-check
--no-first-run
--enable-logging=stderr
--log-level=0
--headless
--disable-dev-shm-usage
--no-sandbox
--user-data-dir=/home/seluser/.config/google-chrome/default


I am starting Docker with the following parameters:

docker run -d \
    -p 4444:4444 \
    -v "$(pwd)"/uk-qa-race-ui/xml-files:/app/xml-files \
    --name selenium-chrome \
    --env SE_NODE_GRID_URL=http://localhost:4444 \
    --env SE_NODE_MAX_SESSIONS=4 \
    --env NODE_CONNECTION_LIMIT_PER_SESSION=4 \
    --env SE_NODE_OVERRIDE_MAX_SESSIONS=true \
	selenium-chrome


This is my Surefire config for parallel running of tests:

    <parallel>methods</parallel>
    <threadCountMethods>4</threadCountMethods>
    <perCoreThreadCount>false</perCoreThreadCount>

[selenium-ci]

@jonn-set, thank you for creating this issue. We will troubleshoot it as soon as we can.

Selenium Triage Team: remember to follow the Triage Guide

[selenium-ci]

Hi, @jonn-set.
Please follow the issue template; we need more information to reproduce the issue.

Either a complete code snippet and URL/HTML (if more than one file is needed, provide a GitHub repo and instructions to run the code), the specific versions used, or a more detailed description to help us understand the issue.

Note: If you cannot share your code and URL/HTML, any complete code snippet and URL/HTML that reproduces the issue is good enough.

Reply to this issue when all information is provided. Thank you.

[cgoldberg]

We would need to see code that can reproduce this along with some logging to even begin to troubleshoot this.

[jonn-set]

I will create a project share it here, gimme some time please.