---
title: "QA Agent"
description: "Build test coverage, execute checks, and understand release health in the same project as the work."
---

> 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.

# QA Agent

The QA Agent keeps test planning and execution close to the stories and
requirements they verify. Use the surfaces below to move from coverage design
to evidence about a release.

![Heizen Studio Test Dashboard showing pass rate, total runs, test cases, suites, code coverage, and delivery health summary cards.](/images/heizen-studio/qa-dashboard.png)

| Surface                                               | Use it for                                                                    |
| ----------------------------------------------------- | ----------------------------------------------------------------------------- |
| [Test Dashboard](/studio/qa/test-dashboard)           | See execution status, coverage, delivery health, and exportable QA reporting. |
| [Test Sheet](/studio/qa/test-sheet)                   | Organize suites and cases, edit them quickly, and run them.                   |
| [Test Plans](/studio/qa/test-plans)                   | Group cases for a release or sprint and run them together.                    |
| [Test Environments](/studio/qa/environments)          | Store the environment configuration used by test runs.                       |
| [Test Runs](/studio/qa/test-runs)                     | Open executions and inspect individual run results, evidence, and defects.    |
| [Automated Testcases](/studio/qa/automated-testcases) | Review automated test reports and coverage.                                   |
| [Load Testing](/studio/qa/load-testing)               | Define reusable API load specs and inspect performance runs.                  |
| [Test VAPT](/studio/qa/vapt)                          | Run vulnerability assessment and penetration testing.                         |

## A practical QA workflow

1. Generate or write cases from the story’s acceptance criteria.
2. Store reusable cases in a suite and group the release set in a plan.
3. Configure a named [test environment](/studio/qa/environments).
4. Run the plan, suite, or security checks.
5. Review the run detail and link defects back to [Ticket Tracker](/studio/delivery/tickets).

> **Execution access can be restricted**
>
> Some execution actions are available only to approved users. When a Run button
> is disabled, the UI shows the access message; contact your workspace
> administrator rather than changing the test data to work around it.

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