Integrate Testsigma with Azure DevOps

Microsoft Azure, aka Azure, is a cloud computing service created by Microsoft for building, testing, deploying, and managing applications and services through Microsoft-managed data centers.

Prerequisites

Before you begin, ensure that you have referred to:

1. Documentation on generating API keys.
2. Documentation on getting test plan ID.

How to integrate with Azure DevOps

1. Login to the Azure DevOps account and create a Project. Navigate to Pipelines and click on the New Pipeline to get started.
2. Choose the Version Control System (VCS) where your application code is stored.

3. Choose the repository where your Configuration YAML file is present. Once you select your repository it will take you to the configuration page where you can configure your pipeline.
4. On Configure your pipeline page, if you already have your YAML file in your repo, you can select the option Existing Azure Pipeline YAML file. Otherwise, you can select Starter Pipeline to create a sample YAML file in the selected repository.

In this case, we already had an existing YAML file in the repo. So, once you select the fourth option in the above image, it will take you to a place where you need to enter the branch and path of the YAML file in your repository.

5. Review the CI Configuration after selecting the Branch and Path, click on Continue.

The YAML file contains the following code where you need to enter the filePath of the Generic Shell Script (cicd-api.sh) to run it. For more information on generic shell script, refer to the documentation generic shell script. This Shell script is the one that actually triggers the Test Plan execution and gives you the result of Test plan once it's complete.

# Azure Pipelines YAML file
trigger: master

pool:
  vmImage: 'ubuntu-latest'

steps:
- script: echo Hello, world!
  displayName: Run a one-line script

- task: Bash@3
  displayName: Run Shell Script (./cd-api.sh)
  inputs:
    filePath: ./cd-api.sh

- task: PublishTestResults@2
  displayName: publish test-results
  inputs:
    testResultFormat: JUnit
    testResultsFiles: '**/*junit-report.xml'

In order to Trigger a particular test plan, you just need to add your own Test plan Execution id and the API key in the Shell Script (cicd-api.sh). As shown below:

For more information on configuration of Generic Shell Script, refer to https://testsigma.com/docs/continuous-integration/shell-script/.

6. Test the configuration once the script is set up and reviewed for the pipeline, and click on the Run to start your Job.

Once the Run is initiated, you will see this page:

Once the job has been completed, the Job status will be Success as shown in the image below:

7. Once the job is completed we can see the reports in the Test Plans > Runs.

After clicking on Runs you can select the Test plan for which you want to view the report and then you will be navigated to the page below, and also you can download the JUnit report in XML format.

You can use another shell script to convert the JUnit XML format result into an HTML format.