> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/transformations/create-test-cases.md).

# Create Test Cases

### Overview

Test cases validate requirements through repeatable steps. Linking tests to requirements supports coverage reporting.

### Key Concepts

* **Test case**: steps and expected outcomes
* **Execution result**: pass, fail, blocked, or not run (status set varies)
* **Coverage**: mapping of requirements to test cases

### How It’s Used

Use test cases during system testing and UAT cycles. Use linked coverage for go/no-go readiness decisions.

### Benefits

* Reduced release risk through repeatable validation
* Faster triage through consistent expected outcomes
* Better auditability through recorded execution history

### Setup Steps

{% stepper %}
{% step %}

### Create a test case

1. Navigate to a Project.
2. Open **Testing**.
3. Select **New test case**.
   {% endstep %}

{% step %}

### Define steps and expected outcome

Add clear steps. Define expected outcome as an objective condition.
{% endstep %}

{% step %}

### Link to requirements

Link the test case to one or more requirements. Use links for coverage reporting.
{% endstep %}
{% endstepper %}

### Best Practices

* Create tests only after requirement acceptance criteria is stable.
* Keep tests small and focused.
* Use a consistent naming pattern, such as `{Process} — {scenario}`.

### Summary

Test cases validate scope through repeatable steps. Links to requirements enable coverage tracking.

Related:

* [Testing](/transformations/testing.md)
* [Linking Tests to Requirements](/transformations/linking-tests-to-requirements.md)
* [Requirements](/transformations/requirements.md)


---

# 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://help.transform.ai/transformations/create-test-cases.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.