docker-selenium | Docker images for Selenium Grid | Functional Testing library

by SeleniumHQ Shell Version: selenium-grid-0.18.1 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(9)Vulnerabilities Install Support

kandi X-RAY | docker-selenium Summary

docker-selenium is a Shell library typically used in Testing, Functional Testing, Docker, Selenium applications. docker-selenium has no bugs, it has no vulnerabilities and it has medium support. However docker-selenium has a Non-SPDX License. You can download it from GitHub.

Docker images for the Selenium Grid Server

Support

Quality

Security

License

Reuse

Support

docker-selenium has a medium active ecosystem.

It has 6799 star(s) with 2399 fork(s). There are 270 watchers for this library.

It had no major release in the last 12 months.

There are 33 open issues and 1208 have been closed. On average issues are closed in 39 days. There are 3 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of docker-selenium is selenium-grid-0.18.1

Quality

docker-selenium has 0 bugs and 0 code smells.

Security

docker-selenium has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

docker-selenium code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

docker-selenium has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

docker-selenium releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

It has 311 lines of code, 19 functions and 5 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of docker-selenium

Get all kandi verified functions for this library.

docker-selenium Key Features

No Key Features are available at this moment for docker-selenium.

docker-selenium Examples and Code Snippets

No Code Snippets are available at this moment for docker-selenium.

Community Discussions

Trending Discussions on docker-selenium

Selenium is skipping the test and throwing the error "SessionNotCreatedException: Could not start a new session" while executing on container

using docker compose to run selenium hub and node

Add more instances to Selenium Docker

How to configure proxy in selenium/standalone-chrome docker image using my docker-compose

Can I run two isolated Google Chrome windows using a single Selenium driver?

AWS-Linux-Docker-Selenium grid Cannot start service chrome: port is already allocated error

Teamcity + Docker:selenium/standalone-chrome file download issue

Test in docker-selenium can download file when running locally but not on Jenkins

How to clean up waiting requests after Selenium webdriver connection timeout

QUESTION

Selenium is skipping the test and throwing the error "SessionNotCreatedException: Could not start a new session" while executing on container

Asked 2021-Dec-27 at 13:46

I am executing the Selenium tests usinng TestNG on selenium standalone chrome debug docker container.

Below is the Selenium code to instantiate remote web driver:

...

ANSWER

Answered 2021-Dec-27 at 13:46

I just looked at selenium/standalone-chrome-debug:latest layer #16 and there is the following command:

Source https://stackoverflow.com/questions/70494502

QUESTION

using docker compose to run selenium hub and node

Asked 2021-Jul-09 at 21:06

I have this docker-compose.yml file from here that I am using to open selenium hub and node on mac OS . I changed host port to 65299 , as I got error that 4444 is being used. I have docker desktop 3.5.1 installed

...

ANSWER

Answered 2021-Jul-09 at 21:06

The HUB_PORT variable of nodes are wrong. 65299 port is the port for accessing hub from outside of docker network. For example you are using this port the access hub from browser.

You need to set 4444 to that variable. That port available to docker network. So nodes can connect hub.

Source https://stackoverflow.com/questions/68322524

QUESTION

Add more instances to Selenium Docker

Asked 2021-Jun-02 at 12:59

I have downloaded Selenium Grid from a Docker compose, following the documentation. Now, I have all the images up and running.

Also, the UI is working.

For each browser, I have only one instance. I want to increment the number of instances for each browser. So, I can run parallel tests. I can't find the way to do that.

...

ANSWER

Answered 2021-Mar-02 at 14:12

You need to add the environment variable NODE_MAX_CONCURRENT_SESSIONS for the node you would like to set the concurrency for.. For example:

Source https://stackoverflow.com/questions/66440577

QUESTION

How to configure proxy in selenium/standalone-chrome docker image using my docker-compose

Asked 2021-May-25 at 15:45

I am using this docker image:

https://hub.docker.com/r/selenium/standalone-chrome/

In my docker-compose:

...

ANSWER

Answered 2021-May-25 at 15:45

Using the environment http_proxy worked for me:

Source https://stackoverflow.com/questions/67654261

QUESTION

Can I run two isolated Google Chrome windows using a single Selenium driver?

Asked 2021-Apr-22 at 14:55

I would like to test interactions between two logged in users on a website that only allows a single user to be logged in for a given browser session. The reason I'd like to avoid creating a second driver is because I'd prefer to use Selenium's provided Docker containers to run my tests (https://github.com/SeleniumHQ/docker-selenium), which seem to operate on a "one port-one driver" basis, with only a single exposed port. Selenium Grid is not an option due to the pipeline environment these tests will be running in.

The two windows do not need to be able to run actions concurrently, but since my test case is two logged-in users interacting with each other, neither user can log out while the other user is performing actions.

Using two drivers in my own Docker container is my last resort, as I've found it to be less fast and reliable than Selenium's own containers, but I'll go that route if I have no other option.

...

ANSWER

Answered 2021-Apr-22 at 14:55

The solution is that what I was trying to do was not possible. However, for my use case, I was able to spin up an additional Selenium provided Docker image that would be listening on a different port, allowing me to set up two drivers.

Source https://stackoverflow.com/questions/67133314

QUESTION

AWS-Linux-Docker-Selenium grid Cannot start service chrome: port is already allocated error

Asked 2021-Jan-26 at 13:48

I am using AWS-Linux-Docker-Selenium grid configuration to run selenium tests. docker-compose up is running fine and I am able to see single containers for chrome,firefox,opera.

...

ANSWER

Answered 2021-Jan-26 at 13:48

This happens because your node is configured to expose VNC port to a certain port of host and when you start several nodes they all try to bind on that port.

Instead of:

Source https://stackoverflow.com/questions/65902022

QUESTION

Teamcity + Docker:selenium/standalone-chrome file download issue

Asked 2020-Sep-29 at 13:11

I am running my selenium test suite in Docker and configured with Teamcity for CI. I have one test case to verify file download which is working fine if I am running from my linux machine and It's getting failed on running through Teamcity.

Below could be the reason which I got from another post but I am not able to solve this.

When running "docker-compose up" if you don't have the "download" folder created (host machine) it creates the folder with root permissions and with no write permissions preventing chromedriver from downloads files.

https://github.com/SeleniumHQ/docker-selenium/issues/548#issuecomment-346073488

This is my docker-compose file

...

ANSWER

Answered 2020-Sep-29 at 13:11

For changing files and directories in TeamCity, I add a build step to the build config before the tests are run. Just use the command line runner type, with something like chmod +X /home/seluser/Downloads

Source https://stackoverflow.com/questions/64049728

QUESTION

Test in docker-selenium can download file when running locally but not on Jenkins

Asked 2020-Mar-17 at 13:14

Using ruby, capybara, docker-selenium:3.141.59-zirconium,

...

ANSWER

Answered 2020-Mar-17 at 13:14

Update /home/seluser/Downloads in order to write to it. Or download to /tmp instead

Source https://stackoverflow.com/questions/60687310

QUESTION

How to clean up waiting requests after Selenium webdriver connection timeout

Asked 2020-Mar-12 at 08:15

Hi I have question about Selenium hub capacity/waiting for slots

Using docker-selenium:

hub: selenium/hub:3.141.59-zirconium
node: selenium/node-chrome-debug:3.141.59-zirconium
python lib: selenium==3.141.0

Python connection code:

...

ANSWER

Answered 2020-Mar-12 at 08:15

I still don't know how to clean this waiting requests. But maybe is better to use server timeout than client timeout. So use newSessionMaxWaitTimeInSeconds flag when running Selenium instead of client timeout.

That's solves most of my problems right now.

Source https://stackoverflow.com/questions/60617024

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install docker-selenium

Point your WebDriver tests to http://localhost:4444. (Optional) To see what is happening inside the container, head to http://localhost:7900 (password is secret). More details about visualising the container activity, check the Debugging section. :point_up: When executing docker run for an image that contains a browser please use the flag --shm-size=2g to use the host's shared memory. :point_up: Always use a Docker image with a full tag to pin a specific browser and Grid version. See Tagging Conventions for details.
Start a Docker container with Firefox
Point your WebDriver tests to http://localhost:4444
That's it!
(Optional) To see what is happening inside the container, head to http://localhost:7900 (password is secret).

Support

Do you need help to use these Docker images? All the contact points for the different Selenium projects can be seen at: https://www.selenium.dev/support/.

Find more information at: