> 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/test-organization-and-views.md).

# Test Organization and Views

### Overview

Test cases grow quickly during delivery.

Views keep execution organized and reviewable.

{% hint style="info" %}
Screenshot placeholder: test case list with filters and a saved-view menu.
{% endhint %}

### Key Concepts

* **Test case**: verification step tied to scope
* **Phase**: execution grouping, such as system test or acceptance test
* **Status**: readiness and outcome signal
* **Save View**: repeatable view configuration for execution

### How It’s Used

Use test views during execution cycles.

Use them during governance to review readiness and defects.

### Benefits

* Faster execution through standardized views
* Cleaner handoffs across testers
* Better coverage visibility when tests link to requirements

### Setup Steps

{% stepper %}
{% step %}

### Define minimal fields

Use a minimal structure:

* **Status**: Draft → Ready → In progress → Passed/Failed
* **Phase**: System test, acceptance test, regression
* **Priority**: High/Medium/Low
* **Owner**: one accountable Teammate
  {% endstep %}

{% step %}

### Open Tests

1. Open the Project.
2. Go to **Tests**.
3. Choose List or Board view (if supported).
   {% endstep %}

{% step %}

### Filter and group for execution

Common execution views:

* `UAT — Ready to run` (Phase = UAT, Status = Ready)
* `UAT — Blocked` (Status = Blocked)
* `Failed — Needs retest` (Status = Failed)

{% hint style="info" %}
Screenshot placeholder: grouping by Status with a Phase filter applied.
{% endhint %}
{% endstep %}

{% step %}

### Save and share

1. Click **Save view**.
2. Name it with a consistent prefix.
   * For example: `Tests — UAT — Ready`
3. Share to the team when Project permissions allow sharing.
   {% endstep %}
   {% endstepper %}

### Best Practices

* Keep status meanings consistent across execution cycles.
* Keep phase names consistent across Projects when possible.
* Link tests to requirements early for coverage reporting.

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

### Troubleshooting

<details>

<summary>My test list looks empty</summary>

Check:

* Project selector (when multiple Projects exist)
* Filters (Phase, Status, Owner)
* Archived or hidden items

Quick fix: clear filters, then reapply.

</details>

<details>

<summary>Status meaning differs across teams</summary>

Pick a minimal workflow.

Keep “Draft” and “Ready” separate.

That prevents half-written tests from entering execution.

</details>

### Summary

Test views keep execution structured.

They also make governance review faster and more consistent.

Related:

* [Create Test Cases](/transformations/create-test-cases.md)
* [Linking Tests to Requirements](/transformations/linking-tests-to-requirements.md)
* [Filtering and Sorting Data](/getting-started/filtering-and-sorting-data.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/test-organization-and-views.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.