Ir al contenido principal

How to create a Selenium Grid using Docker

This is a tutorial for creating a Selenium grid with Docker and Docker Compose using environment variables, above is the vid and below you will find some useful notes.
  1. 1.


    • Have Docker installed
      Have the code for our previous Galen Tests project or your own set of selenium tests locally
  2. 2.

    What is selenium grid

    • Selenium grid is set of services or applications that allows us to create a testing environment in which we can test against different combinations of browsers and operating systems. You can also use it to run tests in parallel.
      Selenium grid consists of two parts. A hub that receives the selenium test commands, like click on this button or enter some text on a textfield, and passes them to the appropriate nodes.
    • And the nodes that register themselves against the selenium hub providing to it the information of each node’s running environment, like, the operating system (for example windows, linux or mac), browser (like firefox or chrome), the version, and so on. The nodes are the ones that run the tests against the actual browsers.
  3. 3.

    How to use envioronment variables in Docker Compose

    • Create a .env file in the same folder as your docker-compose.yml file
      #Add some comments
    • Then, you can use the environment variable inside the docker-compose.yml file
      version: '3'
          image: image
            - "2222:${VARIABLE_NAME}"
    • You can set the environment variables on your OS by calling export
      export HUB_SERVICE_PORT=5555
    • Or you can clear the environment variables by calling unset
      unset HUB_SERVICE_PORT
    • Check the current configurations for Docker Compose given the current values for the environment variables
      docker-compose config
  4. 4.

    How to create a simple selenium grid with a hub and a node using Docker Compose

    • Configure the Selenium Hub
      version: '3'
          image: "selenium/hub"
    • Configure the node (You can replace "BROWSER" below with "chrome" or "firefox" for example)
          image: "selenium/node-BROWSER"
            - HUB_PORT_4444_TCP_ADDR=${HUB_SERVICE_URL}
            - HUB_PORT_4444_TCP_PORT=${HUB_SERVICE_PORT}
            - "hub"
    • Start the hub and the nodes using docker compose
      docker-compose up
    • Check the selenium grid status given the ip for docker containers
    • If you want to scale a particular service (you can replace "SERVICE-NAME=NUMBER-OF" below with "selenium-node-chrome" and "NUMBER-OF-INSTANCES" with 5 for example)
      docker-compose up --scale SERVICE-NAME=NUMBER-OF-INSTANCES
  5. 5.

    Use galen to execute the tests against the local selenium grid

    • Run the galen tests using docker
      docker run -v $(pwd):/workdir -it local/galen test tests/ --htmlreport reports "-Dgalen.browserFactory.selenium.runInGrid=true" "-Dgalen.browserFactory.selenium.grid.url="
  6. 6.


Entradas populares de este blog

Create a custom AEM workflow process step with a dialog

In this tutorial I talk about how to create a custom workflow step process with an additional dialog for configuring it, above is the vid and below you will find some useful notes. 1. Pre-reqs Have access to an Adobe Experience Manager instance. Have Maven installed, understand how it works and also understand how to use Adobe's archetype, you can watch my video about maven here: Creating an AEM application using Maven and Adobe's archetype 2. What is an AEM Workflow and workflow model Workflows allow you to automate different tasks inside AEM by defining a s

Creating Docker containers for Adobe Experience Manager

This is a Docker tutorial for creating a docker image for the Galen framework, above is the vid and below you will find some of the steps followed. Adobe experience manager is a content management system which in a nutshell is an application that allows us to create web sites to be consumed by end users. You might be familiar with other such applications like wordpress or drupal which serves the same purpose A typical deployment would be comprised of two AEM instances, the author instance used for creating and modifying content, the publish instance which serves the content and finally we have a dispatcher which is a static web server used for caching, load balancing and some security purposes. We can configure an AEM instance to work as an author or publish instance by either changing the file name

Creating a Mongo replicaset using docker: Mongo replicaset + Nodejs + Docker Compose

This is a Docker tutorial for creating a Mongo replica set using docker compose and also a couple more containers to experiment with the replica set, above is the vid and below you will find some of the steps followed. Steps Pre-reqs Have node.js installed And docker installed (make sure you have docker-compose as well) Create a container for defining configurations for a mongo instance Create a container for setting up the replica set Create a simple node app using expressjs and mongoose (A modified version from the previous video ) Create a docker-compose file with the mongo and setup containers and two additional containers for experimenting with the replica set Build, Run and experiment with your new containers Create a dockerfile for the first mongo container (not really needed but you could configure more stuff if needed) Include container with mongo preinstalled:  FROM mongo Create default/working directory:  WORKDIR /usr/src/configs Copy mongo