> 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/testing.md).

# Testing

### Overview

Testing validates delivered scope before release. Test cases should be linked to requirements for coverage tracking.

### Key Concepts

* **Test case**: validation steps with expected outcomes
* **Execution**: running test cases and recording results
* **Coverage**: mapping of requirements to test cases
* **Save View**: repeatable testing review list

### How It’s Used

Use test cases to validate requirements. Use linked tests for coverage reporting and go/no-go decisions.

### Benefits

* Reduced release risk through repeatable validation
* Clear audit trail for validation results
* Faster scope impact analysis through linked coverage

### Setup Steps

{% stepper %}
{% step %}

### Create test cases

* [Create Test Cases](/transformations/create-test-cases.md)
  {% endstep %}

{% step %}

### Organize test views

* [Test Organization and Views](/transformations/test-organization-and-views.md)
  {% endstep %}

{% step %}

### Link tests to requirements

* [Linking Tests to Requirements](/transformations/linking-tests-to-requirements.md)
  {% endstep %}
  {% endstepper %}

### Best Practices

* Require acceptance criteria before creating approval-ready tests.
* Keep test statuses consistent across Projects.
* Use Save Views for execution tracking and go/no-go readiness.

### Summary

Testing validates delivered scope through linked test cases. Coverage links support governance and reporting.

Related:

* [Requirements](/transformations/requirements.md)
* [Working with Views](/getting-started/working-with-views.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 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://help.transform.ai/transformations/testing.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.