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


# Why do we need an automation framework?
Running the automated tests is great but if tests fail, we need additional information to troubleshoot the root cause of the failure.

This information comes from different places:
- **The screenshot of the page where the test failed** shows us the page status at the time of failure.
- **The exception** provides information on why the failure was generated.
- **The stack trace** shows the class, method, and line of code that is responsible for the failure.

It is a bad idea to add code for taking screenshots and exceptions to the page or test classes because this leads to having duplicated code and to making the page/test classes have too many responsibilities.

It is better to implement these functionalities as separate classes that are part of an automation framework so they can be used in the page classes when needed.

The classes from the automation framework should be <b>independent of the site</b> to be tested so they can be used in any other automation project.

# What is in the automation framework?
Our automation framework will include classes for

- Creating a driver object for a specific browser
- Taking screenshots
- Saving screenshots to files
- Collecting exceptions and stack traces
- Saving information to logs

A real automation project has many other components that are skipped in our case since our focus is not to implement a full automation framework. Our goal is to run Selenium tests in Azure DevOps. 

To accomplish it, a minimal automation framework with just a few components is sufficient.

Each framework component is described separately in its own section.


Get introduced to the automation framework for implementing standard purpose functionality for taking screenshots, saving logs, and creating a driver.

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

What is in the Automation Framework?

Why do we need an automation framework?