Feature · Closure · Defect tracking
From red row to
filed in one click.
A failed result already contains everything a good bug report needs. One click files it — try it.
✗ expected “link expired” — got form at 00:31:07
The real flow — Record as Bug carries the case, the run and the error output with it.
In the product
How it actually works.
The failure happens
A case fails in a run. The result row keeps the duration, logs and the exact assertion that broke.
Record as Bug
One click creates the defect — pre-linked to the test case and the run that caught it, with the error output attached as evidence. No screenshots-in-Slack archaeology.
Track it to closure
Severity (Critical → Low), status (Open → In Progress → Resolved → Closed → Reopened), assignee, and a detail page per bug. Connected Jira? Failed cases can sync as tickets.
See these steps on screen
coming soonA guided video of this exact flow is being recorded — it will live right here.
Spec sheet