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

It has already been mentioned in the Project Information section (of the Selenium Automation Project chapter) that the project uses Maven for managing dependencies. 

The dependencies are described in the `pom.xml` file:

<project xmlns="http://maven.apache.org/POM/4.0.0" 
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">

 <modelVersion>4.0.0</modelVersion>
 <groupId>selenium</groupId>
 <artifactId>selenium</artifactId>
 <version>0.0.1-SNAPSHOT</version>
 <name>selenium</name>

 <dependencies>
	 <dependency>
	 <groupId>org.seleniumhq.selenium</groupId>
	 <artifactId>selenium-java</artifactId>
	 <version>3.141.59</version>
	 </dependency>
	 
	 <dependency>
 			<groupId>org.testng</groupId>
 			<artifactId>testng</artifactId>
 			<version>6.9.10</version>
 			<scope>test</scope>
	 </dependency>
 </dependencies>
 
 <properties>
 <maven.compiler.source>1.8</maven.compiler.source>
 <maven.compiler.target>1.8</maven.compiler.target>
 </properties>
 
</project>

Maven can do much more than managing dependencies. It also allows you to compile the automation code and execute the automated tests.

Two Maven commands are needed for these purposes.


# `mvn clean`
`mvn clean` cleans up the target folder where temporary files are saved by previous code executions. Cleaning up these temporary files makes sure that the next execution happens in a clean environment.


# `mvn test`
`mvn test` does quite a few things. It downloads any missing Maven or dependency files. In addition, it compiles the automation code, executes the automated tests, and generates the test execution results.


# `mvn clean test`
Instead of running the 2 commands separately, first, `mvn clean` and then `mvn test`, the two Maven commands can be combined into one:
 

```
mvn clean test
```

# Outcome of executing tests
It is important to remember that when running the project's code, the listener runs at the same time with the tests.

So, after the code finishes running, we will have the following:
 
<ul>
<li>Execution status for each test</li>
<li>Screenshots taken for each passing test: They can be found in the target/screenshots folder.</li>
<li>Screenshots taken for each failing test: They can be found in the target/screenshots folder.</li>
<li>Trace log showing the test name and the names of all executed methods for each test: It can be found in the target/logs folder.</li>
<li>Exception log showing the exception info and the stack trace for each failed test: It can be found in the target/logs folder.
<hr/>


> ### Hints
> 1. Execute tests that belong to a group 
>
> If, instead of running all tests, we need to only run the tests that belong to a certain group, let's say the `"High"` group, then the command uses a parameter for the group name:
 
>
> ```
>mvn clean test -Dgroups=High
>```
>
> 2. Execute tests that belong to multiple groups
>
> If we need to run tests that are part of multiple groups, the group names should be separated by a **comma**:
>
>```
>mvn clean test -Dgroups=High,Low
>```

Get introduced to the Maven commands that are needed to  run Java automated tests in the command prompt.


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 Execute Automated Tests With Maven