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

All interactions with the site pages happen in page object classes.

For each web page that is used in the test, a page object class is needed. 

We will use a `HomePage` class for the Home Page and a `ResultsPage` class for the Results Page.

Both page object classes follow the same template.


public class PageObjectClass
{
   private WebDriver driver;

   //element locator variables

   //page url variable
   //page title variable

   public PageObjectClass(WebDriver driver)
   {
      this.driver = driver;
   }

   //methods that interact with the page

   //methods that provide information from the page

}


# Page class constructor
Both classes will have a constructor for creating the class's objects. The constructor gets a driver parameter that is saved in a class variable so the class methods can use it.

# Page class variables
Both classes have a driver variable that gets a value in the constructor. They also have page url variables and element locator variables. Since the URL and locator variables should not have their values changed, they can be declared as constants using the static and final keywords.

# Page object methods
In addition to class variables and class constructors, the page object classes have **page methods**.

The page methods can be

- **`public`** if they are used in the test methods; only a few of the page methods should be public.
- **`private`** if they are used only inside of the class, more specifically, by the public methods; the majority of the page methods should be private.

The methods can also be separated by what they do:

Learn how to set up the page object class that contains the page URL, title, and locators.

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

Page Object Template

Page class constructor