> 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/mcp/mozark-mcp-docs/guides/find-duplicate-test-cases.md).

# Find duplicate test cases

Identify and safely clean near-duplicate test cases.

Large projects accumulate near-identical test cases. Mozark can find them semantically—not just by matching titles.

> *"Find duplicate test cases in this project."*

The assistant runs `find_duplicate_test_cases` and reports groups of similar cases with a similarity score and a suggested keeper.

Review the groups, then decide:

> *"Merge group 2 — keep TC-18 and delete the rest."*

Deletion uses `tcm_bulk_delete_test_cases` and always waits for your explicit confirmation.

{% hint style="info" %}
Deletes in TCM are soft deletes. Contact your Mozark admin if you need something restored.
{% 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.mozark.ai/mcp/mozark-mcp-docs/guides/find-duplicate-test-cases.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.