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

We need to add a few more tasks to the pipeline to get the screenshots from the Docker container.
## Steps to get the screenshots from the container
Since the container stops after executing the Selenium tests, we need to start it again first.

After it is started, we copy the screenshots from the `target/screenshots` folder of the container in a sub-folder of the default working folder of the pipeline.

Finally, we save the screenshots from the default working folder as a pipeline artifact.

## The new pipeline
The new pipeline code is given below:


We need to add a few more tasks to the pipeline to get the screenshots from the Docker container.
# Steps to get the screenshots from the container
Since the container stops after executing the Selenium tests, we need to start it again first.

After it is started, we copy the screenshots from the `target/screenshots` folder of the container in a sub-folder of the default working folder of the pipeline.

Finally, we save the screenshots from the default working folder as a pipeline artifact.

# The new pipeline
The new pipeline code is given below:


Learn how to publish screenshots as artifacts in the Docker pipeline.

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

Save Screenshots as Artifact

Steps to get the screenshots from the container

The new pipeline