> 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/create-and-execute-tests-with-design-studio/working-with-test-case-section/features-in-test-case-section-1/import-and-export-test-case.md).

# Importing and Exporting Test Cases

The Import and Export Test Cases feature helps you move test cases between projects or environments, making it easier to reuse, share, and back up test assets. You can import existing test cases into a project or export test cases with element repository elements. This article explains how to import and export test cases in Avo Assure. 

## Importing Test Cases

To import Test Cases, perform the following actions:

1. On the **Home** page, under **Projects**, select the required project.
2. Go to **Design Studio** > **Test Case**. 
3. Select created test cases and select the **Import Testcase** ( **->]**) icon**.** The **Import** dialog opens. 
4. Select **Choose file**. The **File Explorer** dialog opens.
5. Select the JSON file and select **Open**.
6. Select the Import related elements / repositories checkbox.

{% hint style="info" %}
**Note**: If you do not select the checkbox, Avo Assure uses the existing elements and repositories. If the required elements or repositories are not available in the project, Avo Assure imports them.
{% endhint %}

7. Select **Import**.

![](https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2Ff7P84p1ElmosiGA16adX%2Funknown.png?alt=media\&token=72abce20-9c99-4ca5-b1b9-e86a941b4d06)

## Exporting Test Cases

To export Test Cases, perform the following actions:

1. On the **Home** page, under **Projects**, select the required project.
2. Go to **Design Studio** and select the **Test Case** tab. 
3. Select created test cases and select the **Export Testcase** (**\[<-**) icon. The **Export** dialog opens.&#x20;

{% hint style="info" %}
**Note**: You can change the test case name during export. The exported file is saved in the **Downloads** folder.
{% endhint %}

4. Select **Export**. The **Data Exported Successfully** message appears.

![](https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FraFI8tbblI20bNeGpflQ%2Funknown.png?alt=media\&token=a4ed5332-b7e7-4383-9d8e-9b4223b2bb8a)


---

# 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/create-and-execute-tests-with-design-studio/working-with-test-case-section/features-in-test-case-section-1/import-and-export-test-case.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.