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

A good test automation solution includes more than just test and page object classes. It should have support for collecting debugging information if any test fails. This means taking screenshots, collecting exceptions and stack traces, and saving them to a log file.

# Do not take screenshots/logs in test methods
It is a bad idea to take screenshots and collect exceptions/stack traces with `try/catch` statements in the test method as it leads to code duplication:

@Test(groups = "Medium")
public void any_Page_Has_Results_Test() 
{
   try
   {	
         HomePage homePage = openHomePage();

         ResultsPage resultsPage = homePage.searchFor(KEYWORD);	    	    	    
         Assert.assertEquals(resultsPage.resultsPerPage(), "1 to 10");
	    
         ResultsPage resultsPage3 = resultsPage.goToPage(3);	    
         Assert.assertEquals(resultsPage3.resultsPerPage(), "21 to 30");

         ResultsPage resultsPage5 = resultsPage3.goToPage(5);	    
         Assert.assertEquals(resultsPage5.resultsPerPage(), "41 to 50");
   }
   catch (Exception e)
   {
          //take screenshot
          //log exception and stack trace
   }
}

# Do not take screenshots/logs in page methods
It is also a bad idea to use `try/catch` statements in the page methods for taking screenshots and logs for the same reason (code duplication):

Understand why the TestNG listeners are a better way of capturing screenshots and logs.

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

How to Take Screenshots and Exceptions

Do not take screenshots/logs in test methods

Do not take