Learn how to run Selenium Java tests in Azure DevOps.

Mastering Selenium

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 module.
 
In this module, we’ll 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.

Run Selenium Java Tests in Azure DevOps

## Get the name of the container where the tests were executed

Use the command `docker ps -a`:



docker ps -a

CONTAINER ID   IMAGE   COMMAND             CREATED      STATUS     NAMES
03efc6403f78   tests   "bash command.sh"   7 mins ago   Exited     loving_payne


The output shows that the container exited after the tests finished.

| **Container Id** | **Image** | **Status**| **Names** | 
| --- | --- | --- | --- |
| 03efc6403f78 | tests | Exited | loving_payne |

> Docker assigns randomly generated `Container-Id` and `Name` to each container. Every time you run a container, the container will randomly generate an id and name for it.

It is also possible to define the container name in the `docker run` command. We will do this when running the tests in a Docker pipeline.

## Start the container
Use the `docker start` command and the container name:


# Get the name of the container where the tests were executed

Use the command `docker ps -a`:




The output shows that the container exited after the tests finished.

| **Container Id** | **Image** | **Status**| **Names** | 
| --- | --- | --- | --- |
| 03efc6403f78 | tests | Exited | loving_payne |

> Docker assigns randomly generated `Container-Id` and `Name` to each container. Every time you run a container, the container will randomly generate an id and name for it.

It is also possible to define the container name in the `docker run` command. We will do this when running the tests in a Docker pipeline.

# Start the container
Use the `docker start` command and the container name:


Learn how to access and display the log files.


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

Conclusion

Appendix

Display the Log Files

Get the name of the container where the tests were executed