Overview
When you trigger generation for a test flow, Checksum:- Plans what to build (in Deep mode)
- Implements the test — writing both a story file (
.checksum.md) and a test file (.checksum.spec.ts) - Reviews its own work for quality and correctness
- Verifies the tests pass by actually running them
- Opens a PR to your repository with the generated tests
Triggering Generation
- Navigate to Test Generation in the sidebar
- Select a collection and find the test flow you want to generate
- Click Generate on the test flow
- Choose Standard or Deep mode (see Deep vs Standard)
- The agent session starts

Generation Statuses
As the agent works, your test flow’s status updates:| Status | Meaning |
|---|---|
| Idle | No generation in progress for this test flow |
| Queued | Generation is queued and will start shortly |
| Running | The AI agent is actively generating tests |
| Verifying | Tests are being verified (actually executed) |
| Completed | Tests are generated and PR is ready |
| Failed | Generation encountered an error |
| Aborted | Generation was cancelled |
| Edited | Generated tests were manually edited |
| PR Merged | You merged the generated tests PR |
| PR Closed | You closed the PR without merging |
What Gets Generated
For each test flow, Checksum generates:- Story file (
.checksum.md) — A human-readable description of the test with steps, data setup, and verifications - Test file (
.checksum.spec.ts) — Production-ready Playwright test code
Reviewing Generated Tests
When generation completes, Checksum opens a PR to your test repository. You can:- Review the PR on GitHub/GitLab — read the test code, check the story file
- Run the tests locally — checkout the branch and run
npx checksumai test - Request changes — if something needs adjusting, you can edit directly or re-trigger generation
- Merge — when you’re satisfied, merge the PR to add the tests to your suite