---
title: "Test Sheet"
description: "Organize suites and cases, edit them in a spreadsheet-style view, and run them."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.heizen.work/llms.txt
> Use this file to discover all available pages before exploring further.

# Test Sheet

**QA Agent → Test Sheet** is both the reusable library of QA coverage and the
fast editing surface for it. Suites group cases; cases describe behavior;
steps explain how to execute the check; and each row links back to run status,
category, and the related story or task.

![Heizen Studio Test Sheet showing suites grouped by name, case rows with type, steps, run status, category, and a Run action per row.](/images/heizen-studio/test-sheet.png)

## Create the structure

1. Open **QA Agent → Test Sheet**.
2. Choose **New Suite** and give it a stable purpose, such as “Checkout
   regression.”
3. Choose **Add Test Case** to add a case to a suite.
4. Click the **Steps** cell to open the case detail and add preconditions,
   steps, expected results, and attachments.

Keep a suite small enough that its run result explains a meaningful release
slice. Keep each case focused on one behavior with explicit preconditions,
steps, and expected results so a different tester can execute it without a
conversation.

## Edit quickly

Click **Category** or **Status** on a row to change them inline, and
double-click a **Title** to rename it. Use **Merge suites** to combine
duplicate suites, and the **Suite**, **Type**, and **Category** filters to
narrow a large sheet. Switch between **Table** and **List** view depending on
whether you need the full grid or a scannable list.

## Generate and maintain coverage

From a story, use the QA action to generate cases from the story's acceptance
criteria. For a fixed ticket, create a regression case that reproduces the
original failure and verifies the expected behavior. Review generated cases
in the sheet before running them.

## Run a case

Choose **Run** on a case row to execute it against the selected **Env** and
**Device**. The row's run status updates in place, and the external-link icon
next to a recent run opens the full result with step-by-step evidence and any
linked defects.

## How it works

Cases are reusable records. A [test plan](/studio/qa/test-plans) references
cases rather than copying their content, so a case improvement benefits future
runs while historical run results remain evidence of what happened at that
time.

> **Keep case status honest**
>
> Update a case after its steps or expected result change. A stale passing
> status is worse than an explicit case that needs review.

> **Tie every important case to product intent**
>
> A case linked to a story is easier to review when the product
> changes and easier to explain when a run fails.

Source: https://docs.heizen.work/studio/qa/test-sheet/index.mdx