# Azure Devops

Automate your CI/CD pipeline executions directly from Azure DevOps using SimplifyQA’s native integration. This integration enables seamless test execution as part of your build and release pipelines.

### Prerequisites

Before setting up the integration, ensure the following:

* You have an active SimplifyQA subscription
* An agent is installed and running on the machine for execution
* You have an active Azure DevOps subscription
* An organisation is already created in Azure DevOps

***

### Create a Pipeline in SimplifyQA

1. Log in to your SimplifyQA account
2. Navigate to the **Pipelines** section from the left-hand panel.

<figure><img src="/files/CVfvkb3CVHzgso8QN6n9" alt=""><figcaption></figcaption></figure>

3. Click on **+Pipeline** to create a new one.

<figure><img src="/files/hXcQj4QqOopymXGRX0iR" alt=""><figcaption></figcaption></figure>

4. Enter a meaningful name for your pipeline.

<figure><img src="/files/5dROO9qvUCudexOSNjbW" alt=""><figcaption></figcaption></figure>

5. Enter the required details and click on save to create the pipeline

<figure><img src="/files/d3YPSj2LMUHlS8NPI6Yt" alt=""><figcaption></figcaption></figure>

#### Configure the pipeline details:

* **Pipeline Type:** Choose whether you want to run on **Test Case** or **Suite**
* **Execution Type:** Choose whether you want to run on **Local** or **Cloud**
  * **Local Execution**

    If you choose to run tests locally:

    * Select **Local** under Execution Type.
    * You must specify the **Local Machine Name** where the SimplifyQA Agent is installed and running.
  * **Cloud Execution**

    If you opt for Cloud Execution, you need to register your execution environment on the cloud first. This allows to spin up virtual machines or containers for remote execution. Refer to [Cloud Configuration](/marketplace/integrating-with-cloud-platforms/vm-based.md) to configure your cloud.
* **Test Case/Suite ID:** Enter the corresponding ID
* **Version & Execution Type:** Select the desired versions
* **Machine Name:** Specify the machine for test execution
* **Environment:** Choose the target environment
* **Release and Sprint:** Define these for tracking purposes

***

### Install SimplifyQA Extension in Azure DevOps

1. **Log in** to your Azure DevOps account.
2. From the dashboard, click on the respective project card.

<figure><img src="/files/eRbyXQLBBoTPkWmjkpD7" alt=""><figcaption></figcaption></figure>

3. Click on **Azure Marketplace** and search for **"SimplifyQA"**.

<figure><img src="/files/aNzvSWTQX5nv1hOXIkhF" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/zXHWCqKaVfDEO8T366Bc" alt=""><figcaption></figcaption></figure>

4. Click **Get it for free**.

<figure><img src="/files/L0hu8u7vUHI3P9Wlu9xv" alt=""><figcaption></figcaption></figure>

5. If you already have an organization, proceed to **Downloads**. If not, create one and then download the extension.

***

### Configure Azure DevOps Pipeline

1. Go back to your **Azure DevOps homepage**.
2. Navigate to **Pipelines > Pipelines** from the left panel.

<figure><img src="/files/bml7WyDef114eXTjMQcJ" alt=""><figcaption></figcaption></figure>

3. Click on **New Pipeline.**

<figure><img src="/files/KO4Ck1pfQp2o24fJcm5G" alt=""><figcaption></figcaption></figure>

4. Select the **code repository** you're working with.

<figure><img src="/files/hYSIdmpeDcDsKu3VJQBA" alt="" width="563"><figcaption></figcaption></figure>

5. Authenticate and **log in to the repository**.
6. Select the specific **repository** you want to work on.

<figure><img src="/files/IitFFVTuLck4cW3kgOYn" alt="" width="563"><figcaption></figcaption></figure>

7. Choose **Starter pipeline**.

<figure><img src="/files/I20Tuu5qATlmwIkGgdAE" alt="" width="563"><figcaption></figcaption></figure>

8. Your yaml file will open.

***

### Add SimplifyQA Executor to Pipeline

* Click on **Show assistant** on the right panel.

<figure><img src="/files/MQcZ3tOoGAlUkI4SzT7Z" alt=""><figcaption></figcaption></figure>

* Search for **SimplifyQA** and select **"SimplifyQA Pipeline Executor v2"**.

<figure><img src="/files/0wvj7nRnS65FYWf8sY30" alt=""><figcaption></figcaption></figure>

* Fill in the required details:

  * **Pipeline ID:** The ID from the pipeline created in SimplifyQA
  * **API URL:** Your SimplifyQA base URL
  * **Threshold:** Sets the minimum pass percentage for the test suite. If the actual result falls below this value, the CI/CD pipeline will fail.&#x20;
    * By default, the threshold is set to 100%.
    * For example, if you set the threshold to 70%, the pipeline will still pass even if up to 30% of the tests fail.
  * **Verbose Flag:** When set to TRUE, it enables detailed execution logs, which are helpful for debugging and reviewing test steps in depth. If set to FALSE, only minimal or summary-level logs will be displayed.
  * **API Key:** Your SimplifyQA Machine registration token.&#x20;
    * **Go to Profile > Manage Account > Security >  Create & Manage API Token**.
    * Click **Generate Token**, name your token, and click **Save**.
    * Copy the generated API key and paste it into the configuration.

{% hint style="success" %}
**Note -** If your machine is not registered kindly refer to [Register your Machine](/simplifyqa-installation-and-setup/register-your-machine.md)
{% endhint %}

<figure><img src="/files/Z8lHAByLBvXylNrI4w4J" alt=""><figcaption></figcaption></figure>

* Click **Add** – the task will be added under the **steps** section of your YAML.

<figure><img src="/files/Ja4IPTg5kEpAnORSTCZ3" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/R7lXrWDsrvF5ngrtOesa" alt=""><figcaption></figcaption></figure>

***

### Save and Run the Pipeline

1. Click Save or Save and Run

<figure><img src="/files/351Qlv1mzQk6obMcDJdZ" alt=""><figcaption></figcaption></figure>

2. Select the **branch** and click on **Run Pipeline**.
3. Go to the **Summary tab** to monitor the execution.
4. Click on **Job** to view execution logs, results, and detailed output.

<figure><img src="/files/kcQapQZhWQ2mzmlt6G3V" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/UWEPkUCZaOqYZDLOLUDg" alt=""><figcaption></figcaption></figure>

Once integrated:

* Test pipelines from SimplifyQA can be triggered automatically via Azure DevOps.
* Execution statuses and results can be monitored from both platforms.
* You maintain a single source of truth for test validation in your CI/CD workflow.

***

### Frequently Asked Questions (FAQs)

<details>

<summary>What is the benefit of integrating Azure DevOps with SimplifyQA?</summary>

The integration enables automated triggering of test pipelines in SimplifyQA directly from your Azure DevOps builds or releases. This ensures quality checks are embedded within your CI/CD workflow, catching bugs earlier in the development cycle.

</details>

<details>

<summary>Do I need to write a YAML file manually?</summary>

No, you can use the Starter Pipeline in Azure DevOps, then add the SimplifyQA executor task using the "Show assistant" panel in the pipeline editor.

</details>

<details>

<summary>Can I monitor SimplifyQA test results in Azure DevOps?</summary>

Yes. Once the pipeline is triggered, you can:

* View execution logs in the Jobs tab of Azure
* Monitor detailed test results in SimplifyQA

</details>

<details>

<summary>What happens if my test threshold is not met?</summary>

If configured, the pipeline will fail when the test success rate falls below the set threshold, enforcing test quality as part of CI/CD validation.

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.simplifyqa.ai/marketplace/integrating-with-ci-cd-tools/azure-devops.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.