Test report
A test report records the execution results of test cases in a spec at a specific point in time. Once created, the test case content captured in the report is immutable—updating a test case later does not change past reports.
Lifecycle
NOT_STARTED → IN_PROGRESS → COMPLETED
↓
ABORTED → IN_PROGRESSAn aborted report can be reopened and moved back to IN_PROGRESS.
Results
Each test case result is recorded as one of the following:
| Result | Meaning |
|---|---|
| OK | Passed |
| NG | Failed |
| SKIP | Skipped |
| — | Not yet recorded |
The completion rate (number of recorded results / total cases) is calculated automatically.
Report notes
A free-text notes field is available on each report. Notes are also shown on the public sharing page.
Sharing
Reports can be shared via a public URL. Anyone with the link can view the report without a Katatan account. Shared links expire after 1–30 days (configurable per link) and can be revoked manually at any time.
The shared view shows the spec name, completion rate, report notes, and the full result table including test content, result, tester, and notes.
Export
Reports can be exported to CSV (UTF-8 with BOM, gzip-compressed). The export includes:
- Test subject, preconditions, steps, expected result
- Result (OK / NG / SKIP)
- Tester
- Notes
Webhook
If a webhook is configured on the test spec, a notification is sent when the report status changes to COMPLETED (all results recorded). See Project › Webhooks for configuration details.
Batch result update
Up to 100 test case results can be updated in a single MCP tool call (batch_update_test_results). This is the recommended method for CI/CD pipeline integration when reporting large numbers of results at once.