> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/integrations-in-avo-assure/versioning/azure-devops/configuring-azure-devops-in-avo-assure/pulling-data-from-bitbucket-repository.md).

# Pulling Test Cases from Azure DevOps Repository

The Pull method retrieves test artifacts from the Azure DevOps repository and imports them into Avo Assure. You can restore an existing test case, create a new test case from a previous version, or compare previously pushed test cases with the current test case.

This article explains how to pull test cases from the Azure DevOps repository and use the available pull actions.

{% hint style="info" %}
**Note**: The following steps are the same for all artifacts (Element Repository, Data Table and Execution).
{% endhint %}

To pull test cases from the Azure DevOps repository, perform the following actions:

1. On the **Home** page, under **Projects**, select the required project. 
2. Select **Design Studio** > **Test Case**. 
3. Select the **Bitbucket** icon. 
4. Select **Pull**. The **Pull Test Cases** dialog opens.
5. Select the branch from **Branch** dropdown.
6. Select one or more pushed test artifacts.

{% hint style="info" %}
**Note:** Select the **Pull associated test data and repositories** checkbox. This option pulls the associated **Element Repository** or **Data Table**.
{% endhint %}

7. Select **Pull**. The following actions are available:

<details>

<summary><strong>Restore test case</strong></summary>

To restore the selected test cases to the previously Pushed test cases, perform the following actions:

1. In the **Pull Test Cases** window, select one or more test cases.&#x20;
2. Select **Pull** > **Restore testcase**. The **Restore test cases** dialog opens.&#x20;
3. Review the selected test cases.&#x20;
4. Select **Restore All**.

The selected test cases are restored to the previously pushed test cases.

{% hint style="info" %}
**Note:** Select **Back** to return to the **Pull Test Cases** window without restoring the selected test cases.
{% endhint %}

<img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FYet75AU01srDKjB7PPyQ%2Funknown.png?alt=media&amp;token=6fa92f02-c9ad-46cc-b21d-7c798ade568b" alt="" height="311" width="628">

</details>

<details>

<summary><strong>Restore to new testcase</strong></summary>

To restore the selected test cases as new test cases, perform the following actions:

1. In the **Pull Test Cases** window, select one or more test cases.&#x20;
2. Select **Pull** > **Restore new testcase**. The **Restore new testcase** dialog opens.&#x20;
3. Select **Use same folder name for all selected items** to use the same folder name for all selected test cases.
4. For each selected test case, verify the following details:&#x20;
   * Review the test case details.
   * If required, select the **Add new Folder** checkbox to create a new folder for the restored test case.
   * Enter the valid **Folder name**.

{% hint style="info" %}
**Note**: The **Folder name** field is enabled only after you select the **Add new Folder** checkbox.
{% endhint %}

5. Select **Restore all to new**. The selected test cases are restored as new test cases.

{% hint style="info" %}
**Note:** Select **Back** to return to the **Pull Test Cases** window without restoring the selected test cases.
{% endhint %}

<img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FkdnExUDMtMov1qBSwqiq%2Funknown.png?alt=media&amp;token=c9425b1f-ac70-4724-89cf-9bd8ce893f7b" alt="" height="379" width="628">

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.avoautomation.com/avo-assure/integrations-in-avo-assure/versioning/azure-devops/configuring-azure-devops-in-avo-assure/pulling-data-from-bitbucket-repository.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.