SeleniumHQ / SeleniumHQ/docker-selenium

[🐛 Bug]: Unable to interact with browser popups for new images beyond 3.141.59-20210929

Open
#2,074 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

R-awaiting-answer
Dominant language
Go
Stars
8.7k
Forks
2.5k
Avg merge
10h 16m
Merged PRs (30d)
20

Description

What happened?

We are using docker swarm to setup our hub and node configuration. Our automation framework is based on WebdriverIO V6 and everything was working fine till docker-selenium hub/node image version : 3.141.59-20210929. Any later image after this version is causing our code unable to interact with popups, all other browser interactions are working fine. The selenium code is timing out waiting for element to be displayed. The same code works fine on the local laptop with the latest Chrome browser versions. We have updated the chrome driver as needed for example for image node-chrome:4.15.0-20231102 we upgraded chrome driver to 119. Please help identify this issue

Environment:
CentOS Linux release 7.8.2003
node-chrome:4.15.0-20231102 (or any image after 3.141.59-20210929)
hub::4.15.0-20231102 (or any image after 3.141.59-20210929)

Command used to start Selenium Grid with Docker (or Kubernetes)
docker stack deploy -c docker-compose_v3.141.59-20210929.yml Selenium - Working code
docker stack deploy -c docker_compose_4.yml Selenium - Not working (Selenium image version in this yaml file is 4.15.0-20231102)
Relevant log output
Error stack 

Error: element ("//div[@id="markCompleteDialog"]//button[text()="Member View"]") still not displayed after 10000ms
                    at C:\Work\iex\ghix-tools\test\GHIX_UI_Automation_Tests\node_modules\webdriverio\build\commands\browser\waitUntil.js:66:23
                    at Element.elementErrorHandlerCallbackFn (C:\Work\iex\ghix-tools\test\GHIX_UI_Automation_Tests\node_modules\webdriverio\build\middlewares.js:23:32)
                    at Element.runCommandWithHooks (C:\Work\iex\ghix-tools\test\GHIX_UI_Automation_Tests\node_modules\@wdio\sync\build\wrapCommand.js:105:25)
                    at Element.runCommandWithHooks (C:\Work\iex\ghix-tools\test\GHIX_UI_Automation_Tests\node_modules\@wdio\sync\build\wrapCommand.js:100:24)
                    at Element.wrapCommandFn (C:\Work\iex\ghix-tools\test\GHIX_UI_Automation_Tests\node_modules\@wdio\sync\build\wrapCommand.js:67:44)
                    at Element.elementErrorHandlerCallback (C:\Work\iex\ghix-tools\test\GHIX_UI_Automation_Tests\node_modules\webdriverio\build\middlewares.js:44:12)
                    at Browser.waitForElementToDisplay (C:\Work\iex\ghix-tools\test\GHIX_UI_Automation_Tests\tests\base\Browser.js:232:17)
                    at ViewMember.clickOnViewMemberAccount (C:\Work\iex\ghix-tools\test\GHIX_UI_Automation_Tests\tests\pagemodels\CAP\MemberManagement\ViewMemberPage.js:69:17)
                    at World.<anonymous> (C:\Work\iex\ghix-tools\test\GHIX_UI_Automation_Tests\tests\stepDefs\CAP\MemberManagement\ViewMember.steps.js:17:16)
                    at World.executeSync (C:\Work\iex\ghix-tools\test\GHIX_UI_Automation_Tests\node_modules\@wdio\sync\build\index.js:38:22)
                    at C:\Work\iex\ghix-tools\test\GHIX_UI_Automation_Tests\node_modules\@wdio\sync\build\index.js:69:68
Operating System

CentOS Linux release 7.8.2003

Docker Selenium version (image tag)

4.15.0-20231102

Selenium Grid chart version (chart version)

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Compare docker-compose_v3.141.59-20210929.yml with docker_compose_4.yml, then reproduce the popup flow using the supplied node-chrome and hub image tags. Start with tests/base/Browser.js, tests/pagemodels/CAP/MemberManagement/ViewMemberPage.js, and the failing XPath; done means identifying a reproducible cause for the post-3.141.59 image behavior and documenting a working resolution or confirmed incompatibility.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose, javascript
Domain
devops, infrastructure, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.