Why Should You Take This Course?

Learn about the benefits of executing automated tests using Azure DevOps pipelines.

We'll cover the following

While developing automation code, you run it locally to make sure that it does what it is meant to do.

But running the code locally is just the beginning.

Code executed locally runs in the local operating system:

  • On the local laptop
  • On the local monitor
  • With the local antivirus and firewall
  • With the local browsers (which may or may not have the latest version)
  • With your local environment variables
Code execution

If the code works properly as it should locally, does this mean that you are done? No!

Does your code run correctly in other situations?

Running the code locally does not automatically mean that the code will work in other conditions such as:

  • On a different monitor that has a different resolution
  • On a mobile device
  • On different Internet bandwidth
  • On other operating systems
  • On virtual machines
  • On Docker containers

This is why, as soon as the automated code runs correctly locally, you should start executing it in the cloud in the Azure DevOps environment.

In the cloud, you can use virtual machines with different operating systems and different browsers and configurations. You will be able to run the code in Docker containers with headed or headless browsers, sequentially or in parallel.

Only when your code runs in all these situations can you say that your work is done.

This is the 1st benefit of running tests in Azure DevOps. Your code is tested in multiple environments, sequentially and in parallel, to have the certainty that the code runs properly everywhere.

Can other people use your code?

How can other testers run the tests on the development, testing, or staging environments after a new build is deployed?

Also, developers often use application build pipelines to create and deploy new builds by going through a few phases:

Phases
  • Get the code from the source control.
  • Build the code.
  • Run the unit tests.
  • Create the deployment package.
  • Deploy the new build on the desired environment.

Can an application build pipeline run the Selenium automated tests after the new application build is deployed? It cannot, unless the automated tests run through an Azure DevOps automation pipeline. In this case, the application build pipeline can, if completed successfully, trigger the execution of the automation pipeline.

This is the 2nd benefit of running automation code in Azure Devops. The automated tests can be executed automatically after each new build is deployed.

They can also be executed on demand by other testers and developers.

Or, they can be scheduled to run unattended on any schedule (hourly, daily, weekly).

Additional benefits of executing automated tests in Azure DevOps

The 3rd benefit is that in order to use Azure DevOps pipelines, you need to become proficient in several technologies such as

  • Git
  • Maven
  • Docker
  • Yaml
  • Linux
  • Bash
  • Pipelines

This helps improve your skills in technologies that work together with test automation and coding, so you become more versatile and more valuable by way of being an SDET with DevOps skills.

In summary, in this course, you will learn:

  • How to create a framework for your Selenium project
  • How to run tests locally in local browsers and Docker containers
  • How to migrate your code to the CI/CD environment
  • How to run your Selenium tests in Azure DevOps virtual machines using YAML pipelines
  • How to run your Selenium tests in Azure DevOps Docker containers using YAML pipelines

Let’s get started.