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

Publishing the screenshots is very similar to publishing the logs.


- task: PublishBuildArtifacts@1
  displayName: 'Publish Screenshots as Artifact'
  inputs:         
      PathtoPublish: $(System.DefaultWorkingDirectory)/target/screenshots
      ArtifactName: screenshots


The `PathtoPublish` path ends now with the `screenshots` folder. The name of the artifact is `screenshots`.

After executing the pipeline, the screenshots artifact is displayed on the <b>Artifacts</b> page. 
<br/>Expanding it shows the screenshot taken after the automated test passed.

Click the screenshot to download it:


Learn how to publish the automation screenshots 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

Conclusion

Appendix

Publish Screenshots as Artifacts