How to Run Selenium Tests in Docker

Selenium WebDriver is a great and adaptable apparatus that empowers you to run practical tests on your web applications. By running Selenium tests through Docker compartments, you can spare time while making your tests and get all the more testing alternatives. This blog entry will give a diagram of how to run Selenium Tests in Docker. It depends on an online course by execution robotization design Eliran Shani which you can see here. All contents can likewise be found on GitHub, here.

What is Selenium WebDriver?

Before talking about Selenium WebDriver, we should clarify what Selenium is. Selenium is an open source instrument that mechanizes internet browsers and web applications. As it keeps running crosswise over numerous programs and working frameworks and backings various programming dialects and testing systems, there are unlimited potential outcomes to its testing abilities. In this way, what you choose to do with it is dependent upon you.

Selenium has three noteworthy apparatuses. 1. Selenium IDE, a device that recreates contents by recording and playing them back. Selenium IDE is pretty much deplored. 2. Selenium Server (Grid) for running tests in parallel on various machines. 3. Selenium WebDriver, a vigorous, program based relapse mechanization suite, which empowers circulating tests crosswise over numerous conditions. This blog entry will examine Selenium WebDriver.

Selenium WebDriver Benefits

•          Selenium WebDriver is open source, influencing it to free and compact and open to commitments of individuals from everywhere throughout the world. Moreover, you can take in Selenium from talks and assets over the web that are available to everybody. Then again, it has no official help.

•          Selenium WebDriver bolsters numerous dialects, including Python, C Sharp and Java. This empowers adaptability when utilizing it and also making it available to numerous designers. In any case, Selenium requires involvement and comprehension of its capacities and method for work.

•          Selenium WebDriver underpins numerous program composes, working frameworks and stages, including versatile programs, android, Windows, and so forth. In any case, the analyzer should be in a state of harmony with every one of the updates to guarantee smooth testing.

•          Selenium WebDriver is important for Continuous Integration advancement by working with CI instruments, empowering designers to add practical testing to their Continuous Testing process. Be that as it may, Selenium does not have inbuilt detailing capacities, so it requires introducing outsider modules.

What is Docker?

Docker is a product containerization stage that gives virtualization from the working framework level. In Docker, all product parts can be sorted out in holders. This incorporates the working framework, programming, conditions, condition factors, and so forth. Compartments can be shared among various clients, empowering brisk establishment and running of programming and administrations. This makes Docker convenient for mechanization testing, as the important compartment can simply be downloaded and kept running as a major aspect of the robotized test. In any case, Docker is likewise secure in light of the fact that it keeps running as a disconnected procedure on the host machine. Docker can be kept running on any PC on any framework and in addition in the cloud, including Linux, Windows, Mac, Amazon, Azure and then some.

Docker Benefits

•          Docker is open source. This implies you can discover numerous pictures (used to create compartments) on the web and utilize them. Nonetheless, this likewise implies there is no official Docker bolster.

•          Docker can be a basic piece of Continuous Deployment and Continuous Testing, by guaranteeing you have a reliable situation when forming and going into generation. This is on the grounds that arrangements and conditions are looked after inside, and won't change.

•          Docker is separated, secure and convenient. Be that as it may, it requires aptitude as there is no GUI and it doesn't keep running in exposed metal speed.

Essentials

This blog entry demonstrates a demo that uses the accompanying apparatuses:

•          Python, binded with Selenium WebDriver

•          PyTest as a testing structure (you can utilize a system of your inclination, similar to Nose or JUnit)

•          IntelliJ IDEA as IDE

•          ChromeDriver, GeckoDriver (Firefox) or Headless Chrome

•          Docker (introduce here)

•          CI instrument, as Jenkins, or TeamCity. Include the modules you require, as GitHub for the vault association, Allure for announcing, BlazeMeter for execution testing, and so forth.

Making Your Selenium Test in Docker

1. On the off chance that you need to ensure Docker is introduced, open your support and compose the charge Docker – help. On the off chance that you see a rundown of summons, it implies that Docker is introduced.

2. To look at which Docker pictures are introduced, run docker pictures. A picture has every one of the essentials required for the tests. In the subsequent stages, I will demonstrate to you proper methodologies to get pictures that you may miss.

3. Make your Selenium test.

This could be any test, as indicated by the web application you should be tried. This tests imports capacities, imports PyTest, imports By from Selenium, tests blazedemo.com and declares a few pages.

4. Make and fare the requirements.txt document, to actualize your test in Docker. This document incorporates the bundles expected to run the test.

5. Presently it's an ideal opportunity to make a base Dockerfile to help Selenium, Chrome and Firefox

This base Dockerfile makes another, separated holder that incorporates all that you have to run Selenium to peruse Chrome.

Or then again, rather than making the base Dockerfile, you can utilize Docker Hub, scan for "Selenium" and utilize one of the ~2000 compartments that are as of now there.

Presently, put the order in the Dockerfile in the From segment. At the point when the test is run, Docker will pull the picture from the cloud.

The advantage of utilizing Docker Hub strategy is that you don't need to deal with the Dockerfile without anyone else's input. This is likewise an impediment - you have no adaptability or control over compartments. As I would like to think, the adaptability is justified regardless of the exertion.

In your base Dockerfile, ensure you determine the bundle variant you need to test, so the programs are tried accurately.

The test appeared here incorporates:

•          Downloading the programs' WebDriver (Gecho Driver, Chrome Driver)

•          X Server Display - this is essential in light of the fact that there is no UI, so you should introduce it to have a visual perspective of the test.

•          Symlinks to the webdrivers, to interface everything together

6. Store the base DockerFile in the Root organizer.

7. Make an undertaking Dockerfile to help requirements.txt. This will be the Docker filethat utilizes the base picture

8. Store this Docker base document in the venture root.

9. Make a Bash content to organize your test (and make your life less demanding).

The Bash content pronounces PyTest contentions, sets label names, runs the Selenium test, runs the venture picture, produces a XML from the outcomes, and then some. 

10. We are ready to run the script! Run the command:

  

This command runs the bash file, and also points to the specific test to run.

The command created a container from the base Docker file. The first time this happens it will take a few minutes because the container needs to be installed. But next time, the test will run much quicker.