> For the complete documentation index, see [llms.txt](https://docs.mozark.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mozark.ai/test-context-manager-documentation/test-cases/creating-a-test-case/importing-test-cases-from-csv.md).

# Importing test cases from CSV

Import test cases in bulk from a CSV file.

## Importing test cases from CSV

### Before you start

Make sure your CSV includes a title or name column.

Review the source columns before import so the field mapping is easier to validate.

To import test cases from CSV:

1. Open the **Test Cases** page.
2. Click **Import**.
3. Upload your CSV file.
4. Review the detected field mapping.
5. Adjust any column assignments if needed.
6. Preview the imported rows.
7. Click **Import**.

Successfully parsed rows become test cases.

If the import finds duplicate rows, missing required fields, or blank required values, the preview flags those rows and skips them.

You can still import the valid rows in the same file.

To import skipped rows, fix the formatting issues in the CSV and upload it again.

At minimum, your CSV must include a title or name column.

Imported test cases are marked with `Source = CSV_Import`.

<figure><img src="https://95054152-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIgQEgtjvk4zIWyVkgQ5o%2Fuploads%2FdmMJZCqlxwdhFflEoLC8%2FScreenshot%202026-07-01%20at%202.14.44%E2%80%AFPM.png?alt=media&amp;token=2146222a-08c0-47cb-8ddc-5bf25ad56c03" alt=""><figcaption></figcaption></figure>

### Verify the import

Confirm that the imported rows appear in the test case list.

Check that the field values mapped correctly and that the records show `Source = CSV_Import`.

If any rows fail, correct the CSV and import again.


---

# 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.mozark.ai/test-context-manager-documentation/test-cases/creating-a-test-case/importing-test-cases-from-csv.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.