Gain insights into adding Java, TestNG, and Selenium automation projects to Azure DevOps, sharing repositories, and running tests through CI/CD pipelines efficiently.

Dockerfile.tar.gz

Docker Job

Chrome Job

Azure Chrome Job

We all write automated tests using Selenium WebDriver and Java. While developing and testing our automation code, we run it locally on our computers. Others should be able to change or run the code as well. This becomes possible when the code is added to a repository, from which other people can also access it. Once the code is in a repository, it can be executed in a CI/CD environment - such as Jenkins or Azure DevOps - through pipelines. This is the focus of this course. 

In this course, we will add a local automation project built with Java, TestNG, and Selenium to an Azure DevOps project, share the repository with other people and run its tests through pipelines.

Gnani

Thanks for the exemplary course.
It explains clearly the steps and concepts needed for running Java tests in Azure Devops. 
It was easy to learn and very helpful for my job search.

Very helpful course!

Vlad

I acquired a lot of knowledge and ideas that I can use in my day-to-day work.
I am very pleased with this course and highly recommend it to fellow testers.

Very pleased with this course!

Nilanjan

Enjoyed learning about using a strong framework for test automation,  using Docker to run tests and deploying containers on Azure. Overall, a very useful and interesting course for anyone using test automation!

A very useful and interesting course!

Run Selenium Java Tests In Azure DevOps

The pipeline that runs the Selenium tests in a Docker container relies on the `Dockerfile` from the `root` project folder:


FROM selenium/node-chrome
 
COPY . .
 
USER root
RUN apt-get update
RUN apt-get install maven -y
RUN apt-get install openjdk-8-jdk -y
 
ENTRYPOINT ["bash", "command.sh"]

> Add the above `Dockerfile` to the root of your project repository.

# The Docker pipeline
The Docker pipeline YAML code is below:


trigger:
- master

pool:
  vmImage: 'ubuntu-latest'

steps:
- task: Bash@3
  displayName: 'Create Java Test Image'
  inputs:
   targetType: inline
   script: 'docker build -t seleniumtests .'

- task: Bash@3
  displayName: 'Run Java Test Container'
  inputs:
   targetType: inline
   script: 'docker run -e "BROWSER=chrome" --name tests seleniumtests'


The pipeline has only two tasks, one for building the Docker image and the other for running the Docker container using the new image.

# Build the Docker image
The 1<sup>st</sup> task (lines 8–12) builds the Docker image from the files of the default working directory (notice the `.` at the end of the command) where all project files are downloaded when the code is retrieved from the repository. 

> The new Docker image is named `seleniumtests`.

# Run the Docker container
The 2<sup>nd</sup> task (lines 14–18) runs the Docker container. 

The Docker command creates an environment variable in the container with the name `BROWSER` and the `chrome` value. 

> The Docker command gives the new container the name `tests`.

# Build results
After the pipeline has finished execution, 
when we click the task that runs the container, we can see at the end of the console that all Selenium tests passed as well:



Learn how to create the pipeline and execute the Selenium tests using Docker containers.

Introduction

The Selenium Automation Project

The Automation Framework

Run The Automated Tests in Local Browsers

Run The Automated Tests in Docker Containers

Create the Project In Azure DevOps

Run The Automated Tests in Azure DevOps Pipelines

Run the Automated Tests In Pipelines Using Docker Containers

Wrapping Up

Appendix

Create the Pipeline and Run the Tests