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

You do not. Any needed code can be implemented in the page and test classes.

You do not. The Selenium WebDriver framework has everything that is required in an automation project.

The automation framework is required so the project has 3 layers, each layer depending on the layer under it:
 
<ol>
<li>tests</li>
<li>page objects</li>
<li>automation framework</li>
<li>selenium</li>
</ol>

Do you need an automation framework in your automation project?

Do you need an automation framework in your automation project?

The driver object is created in the setUp() method of the test class.

The driver object is created in the setUp() method of the base test class.

The driver  object is created in a DriverFactory class by a getDriver() static method.

Where do you create the driver object?

Because the Base Test class is in the same package as the Listener class

Because the driver variable of the Base Test class is public

Why can the Listener class access the driver variable from the Base Test class?

Why can the Listener class access the driver variable from the Base Test class?

In the test method by using a try/catch around the test code

Where should screenshots be taken?

Because there is no GUI available in the Docker containers

Because the headless mode makes tests more reliable

Why should the driver be created in headless mode when tests run in Docker containers?

Why should the driver be created in headless mode when tests run in Docker containers?

Test your knowledge and understanding by taking the quiz on the automation framework.


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

Automation Framework Quiz