> 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/pushing-data-to-azure-devops-repository.md). # Pushing Data to Azure DevOps Repository ## Push Method in Avo Assure The Push method in Avo Assure sends the latest test artifacts to the Azure DevOps repository. It is used in the following scenarios: * Creating new test artifacts, such as Element Repository, Test Cases, Data Tables, or Execution Lists. * Updating or modify existing test artifacts to save the latest version in Azure DevOps. * Sharing updated test artifacts with the team through Azure DevOps. * Maintaining version history of automation assets for safety and traceability. ### Pushing Test cases to Azure DevOps Repository From Avo Assure, the following test artifact data can be pushed to Azure DevOps for version control: * Element Repository * Test Case * Data Table * Execution List {% hint style="info" %} **Note**: The steps remain the same for all artifacts. Navigate to the respective artifact page, select the required data or parent folder, and push it to Azure DevOps. {% endhint %} To push Test Cases to Azure DevOps Repository, perform the following actions: 1. On the **Home** page, under **Projects**, select the required Project. 2. Select the **Design Studio** button > **Test Case** page. 3. Select the **Azure DevOps** icon. 4. Select **Push**. The **Commit Test Cases** dialog opens.
4. In the **Search** textbox, enter a keyword to filter the test cases. 5. Select the **Status** dropdown to filter the test cases by workflow status. 6. Select **Hide checked in artifacts** to exclude already checked in items. 7. Under **Name**, expand the folders, and then select the required test cases. {% hint style="info" %} **Note**: * The **Status** column displays the workflow status of test artifacts. * The **Checked in** column indicates whether a test case is already pushed to Azure DevOps. * You can view the total number of selected Test Cases. {% endhint %} 8. Select the **Branch** dropdown to choose the Azure DevOps branch. 9. In the **Commit message** text box, enter the description of the push changes. {% hint style="info" %} **Note**: * Select **Push associated Element Repository** to push the associated element repository of the selected test artifact. * Select **Push associated Data Table** to push the associated data table of the selected test artifact. {% endhint %} 10. Select **Push** to commit and push the selected test cases to Azure DevOps. After selecting **Push**, a success message appears. The Client console also provides a confirmation message indicating whether all test artifacts were successfully pushed to Azure DevOps. {% hint style="info" %} **Note**: * During the process of pushing test artifacts to Azure DevOps, the Avo Assure Client Console provides real-time updates throughout the Commit phase, showing the ongoing progress. After the commit is completed successfully, a single push is triggered automatically to Azure DevOps. * You can also compare the test artifacts. For more information, refer to (Link to Comparing Test Artifacts) article. {% endhint %} ### Pushing Data Table to Azure DevOps Repository To push Data Table to Azure DevOps Repository, perform the following actions: 1. On the **Home** page, under **Projects**, select the required Project. 2. Select **Manage Integrations**. The T**est Data Management** page opens. 3. Select the **Azure DevOps** icon. 4. Select **Push**. The **Commit Data tables** dialog opens.
5. In the **Search** textbox, enter a keyword to filter the data tables. 6. Select the **Status** dropdown to filter the data tables by workflow status. 7. Select **Hide checked in artifacts** to exclude already checked in items. 8. Under **Name**, expand the folders, and then select the required data tables. {% hint style="info" %} **Note**: * The **Status** column displays the workflow status of the data table. * The **Checked in** column indicates whether a data table is already pushed to Azure DevOps. * You can view the total number of selected Data Tables. {% endhint %} 8. Select the **Branch** dropdown to choose the Azure DevOps branch. 9. In the **Commit message** textbox, enter the description of the push changes. 10. Select **Push** to commit and push the selected data tables to Azure DevOps. After selecting **Push**, a success message appears. The client **Console** also provides a confirmation message indicating whether all data tables were successfully pushed to Azure DevOps. {% hint style="info" %} **Note**: During the process of pushing data tables to Azure DevOps, the Avo Assure client **Console** provides real-time updates throughout the commit phase, showing the ongoing progress. After the commit is completed successfully, a single push is triggered automatically to Azure DevOps. {% endhint %} {% hint style="info" %} **Note**: To **Compare** the selected test artifacts with the corresponding versions in the Azure DevOps repository before pushing, select Compare. For more information, refer to the Comparing Test Artifacts section. {% endhint %} --- # 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/pushing-data-to-azure-devops-repository.md?ask=&goal= ``` `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.