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

We know where the logs are located during the pipeline execution:


```
$(System.DefaultWorkingDirectory)/target/logs
```
To access them after the pipeline finishes executing, the logs have to be published first by the pipeline as an artifact.


## What exactly is an artifact?
An artifact is an output of a pipeline that can be used by another pipeline or by a user. Examples of artifacts are logs, screenshots, and reports.

## How can an artifact be generated?
An artifact can be generated by adding a new task to the pipeline:



We know where the logs are located during the pipeline execution:


```
$(System.DefaultWorkingDirectory)/target/logs
```
To access them after the pipeline finishes executing, the logs have to be published first by the pipeline as an artifact.


# What exactly is an artifact?
An artifact is an output of a pipeline that can be used by another pipeline or by a user. Examples of artifacts are logs, screenshots, and reports.

# How can an artifact be generated?
An artifact can be generated by adding a new task to the pipeline:



We know where the logs are located during the pipeline execution:


```
＄(System.DefaultWorkingDirectory)/target/logs
```
To access them after the pipeline finishes executing, the logs have to be published first by the pipeline as an artifact.


# What exactly is an artifact?
An artifact is an output of a pipeline that can be used by another pipeline or by a user. Examples of artifacts are logs, screenshots, and reports.

# How can an artifact be generated?
An artifact can be generated by adding a new task to the pipeline:



Learn how to publish the automation logs using the PublishBuildArtifacts task.

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

Publish Logs as Artifacts

What exactly is an artifact?

How can an artifact be generated?