> 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/bitbucket/configuring-bitbucket-in-avo-assure/comparing-test-artifacts-1/comparing-test-artifacts-for-push.md).

# Comparing Test Artifacts Before Push

Comparing the current version with a pushed version helps you review the changes made to a test artifact before pushing it again. This comparison helps you:

* Identify changes between the current version and the previously pushed version.
* Review additions, modifications, and removed items.
* Verify the changes before pushing a new version.
* Compare one or more selected test artifacts in a single comparison session.

## Comparing Current Version Before Push

The Compare option is available in the Push page for all supported version-controlled test artifacts. Use this option to review the differences between the current test artifact in Avo Assure and its previously pushed version before you push the latest changes.

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

To compare the current test artifact with the previously pushed version before pushing the latest changes, perform the following actions:

1. On the **Home** page, under **Projects**, select the required Project.
2. Select **Design Studio** > **Test Case**.
3. On the **Test Case** page, select the **Bitbucket** icon.
4. Select **Push**. The **Commit Test Cases** dialog opens.
5. 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 Bitbucket.
* You can select one or more test cases at a time.
  {% endhint %}

6. You can view the total number of selected Test Cases.
7. Select the branch from **Branch** dropdown.
8. Select **Compare**. The **It may take 1-2 minutes to compare** dialog opens.
9. Select **OK**. The comparison process starts. After the process completes, the **Bitbucket Actions** dialog opens and displays the comparison results including **Test case name**, **Elements**, **Actions**, **Input values**, and **Output values**.
10. Review the differences between the **Current view** and the **Pushed**.\
    The following changes highlighted in the comparison view:
    * **Added**: Indicates that new test cases or test steps are added compared to the previous version.
    * **Edited**: Indicates that existing test cases or test steps are modified.
    * **Removed**: Indicates that existing test cases or test steps are removed from the test case.
    * **No changes**: Indicates that no differences exist between the **Current view** and the **Pushed** test cases.

{% hint style="info" %}
**Note**: If multiple test cases are selected, then select the navigation arrows to navigate

(**< >**) between the test cases.
{% endhint %}

4. Select **Done** to close the comparison view.

{% hint style="info" %}
**Note:** Select **Back** to return to the **Commit Test Cases** window.
{% endhint %}

![](https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2Fokoc6Fsfk9z3HqCcRBaT%2Funknown.png?alt=media\&token=cc262067-aaf4-4c98-a164-3d1e1c030710)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avoautomation.com/avo-assure/integrations-in-avo-assure/versioning/bitbucket/configuring-bitbucket-in-avo-assure/comparing-test-artifacts-1/comparing-test-artifacts-for-push.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.