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 selects the virtual machine to be used for the pipeline execution.

The virtual machine name is `windows-latest`.

The statement defines the pool of virtual machines to be used for the pipeline execution.

The pool name is `windows-latest`.

One of the virtual machines from this pool will be selected and used.

The statement defines the name of the pipeline.

What does this statement do?
 
``` yaml
pool:
 vmImage: 'windows-latest'
```

What does this statement do?
 
<pre><code class="language-yaml">pool:
 vmImage: 'windows-latest'
</code></pre>

It creates a pipeline variable named `BROWSER`.

It creates an environment variable in the virtual machine named `BROWSER`.

What is the purpose of this task?
 
``` yaml
- task: CmdLine@2
 displayName: 'Set Variables'
 inputs:
 script: |
 setx BROWSER chrome
```

What is the purpose of this task?
 
<pre><code class="language-yaml">- task: CmdLine@2
 displayName: 'Set Variables'
 inputs:
 script: |
 setx BROWSER chrome
</code></pre>

Because `setx` is not the correct command

Because chrome should be surrounded by quotes

Because the `BROWSER` variable value should not be hard-coded in the pipeline YAML code

Why is this task incorrect?
 
``` yaml
- task: CmdLine@2
 displayName: 'Set Variables'
 inputs:
 script: |
 setx BROWSER chrome
```

Why is this task incorrect?
 
<pre><code class="language-yaml">- task: CmdLine@2
 displayName: 'Set Variables'
 inputs:
 script: |
 setx BROWSER chrome
</code></pre>

By adding to the task the group as follows:
 
``` yaml
- task: Maven@3
 inputs:
 
 mavenPomFile: 'pom.xml'
 mavenOptions: '-Xmx3072m'
 javaHomeOption: 'JDKVersion'
 jdkVersionOption: '1.8'
 jdkArchitectureOption: 'x64'
 publishJUnitResults: true
 testResultsFiles: '**/surefire-reports/TEST-*.xml'

 group: 'High' <------
 
 goals: 'clean test'
```

To run the tests that belong to a specific group, the group has been mentioned in the goals field. 

The group value should be provided from a pipeline variable:

``` yaml
goals: 'clean test -Dgroups=$(Priority)'
```

To run the tests that belong to a specific group, the group has been mentioned in the goals field as follows:

``` yaml
goals: 'clean test -Dgroups=High'  
```

How do you only run the tests that belong to a particular group in the pipeline ?

How do you only run the tests that belong to a particular group in the pipeline ?

Because it is important that the user can access them after the pipeline finishes executing

Because they may be needed in another pipeline

Because they are needed in the Azure DevOps reports

Why is it important to publish logs and screenshots as artifacts as follows?

``` yaml
- task: PublishBuildArtifacts@1
  displayName: 'Publish Log File as Artifact'
  inputs:         
      PathtoPublish: $(System.DefaultWorkingDirectory)/target/logs
      ArtifactName: logs
```

Why is it important to publish logs and screenshots as artifacts as follows?
<pre><code class="language-yaml">- task: PublishBuildArtifacts@1
 displayName: 'Publish Log File as Artifact'
 inputs: 
 PathtoPublish: $(System.DefaultWorkingDirectory)/target/logs
 ArtifactName: logs
</code></pre>

`TestsPriority` is a variable that gets a different value for each job run.

What is `TestsPriority` for the following strategy?

``` yaml
strategy:
    matrix:
      Tests_High:
        TestsPriority: "High"
      Tests_Medium:
        TestsPriority: "Medium"
      Tests_Low:
        TestsPriority: "Low"
 
    maxParallel: 1  
```

What is <code>TestsPriority</code> for the following strategy?
<pre><code class="language-yaml">strategy:
 matrix:
 Tests_High:
 TestsPriority: &quot;High&quot;
 Tests_Medium:
 TestsPriority: &quot;Medium&quot;
 Tests_Low:
 TestsPriority: &quot;Low&quot;
 
 maxParallel: 1 
</code></pre>

`Tests_High` is the name of the test class.

`TestsPriority` is the variable that defines the tests' priority.

`Tests_High` is the name of the job run.

`TestsPriority` is a variable that gets a different value for each job run.

`Tests_High` is the name of the test group.

`TestsPriority` is a pipeline variable for priority.

What is the difference between `Tests_High` and `TestsPriority` in the following strategy?


``` yaml
strategy:
    matrix:
      Tests_High:
        TestsPriority: "High"
      Tests_Medium:
        TestsPriority: "Medium"
      Tests_Low:
        TestsPriority: "Low"
```

What is the difference between <code>Tests_High</code> and <code>TestsPriority</code> in the following strategy?
<pre><code class="language-yaml">strategy:
 matrix:
 Tests_High:
 TestsPriority: &quot;High&quot;
 Tests_Medium:
 TestsPriority: &quot;Medium&quot;
 Tests_Low:
 TestsPriority: &quot;Low&quot;
</code></pre>

The logs can be found in the following folder:

`$(System.DefaultWorkingDirectory)/target/logs`

Where are the logs generated for the Selenium tests?

Where are the logs generated for the Selenium tests?

The Maven pom file should always be named `pom.xml`.

The goals should also include the clean option before the test.

No group is specified in the goals field.

What is wrong with the following Maven task?
 
``` yaml
- task: Maven@3
 inputs:
 mavenPomFile: 'custompom.xml'
 mavenOptions: '-Xmx3072m'
 javaHomeOption: 'JDKVersion'
 jdkVersionOption: '1.8'
 jdkArchitectureOption: 'x64'
 publishJUnitResults: true
 testResultsFiles: '**/surefire-reports/TEST-*.xml'
 goals: 'test'
```

What is wrong with the following Maven task?
 
<pre><code class="language-yaml">- task: Maven@3
 inputs:
 mavenPomFile: 'custompom.xml'
 mavenOptions: '-Xmx3072m'
 javaHomeOption: 'JDKVersion'
 jdkVersionOption: '1.8'
 jdkArchitectureOption: 'x64'
 publishJUnitResults: true
 testResultsFiles: '**/surefire-reports/TEST-*.xml'
 goals: 'test'
</code></pre>

The user credentials can be hard-coded in the automation code.

The user credentials should be part of a settings file that is not added to the repository.

The user credentials should be specified as masked pipeline variables. Environment variables should be created from the masked pipeline variables.

The user credentials should be hardcoded in pipeline code. Since only specific users have access to the pipeline, this is a good solution.

How can user credentials be used by automated tests?

How can user credentials be used by automated tests?

Test your knowledge and understanding by taking a quiz on Azure DevOps Pipeline.

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

Azure DevOps Pipeline Quiz