QA and the QA agent
Draft and approve test cases from acceptance criteria, run QA test runs, let the QA agent test in a browser, and file bug work orders automatically.
Test cases
Skaftor can draft one test case per acceptance criterion — steps, expected result and test data — when requirements are approved. QA approves, edits, re-drafts or archives each one. Drafts aren't run and don't count towards QA Approval until QA approves them.
QA test runs
On the feature's Deploy tab, under "Before you ship", start a test run against a named build and "Complete run". QA Approval needs a completed run of the latest build with every case passed or waived.
The QA agent
"Run QA agent" carries out the approved cases in a browser on a deployment outside production. For each case it records pass, fail at a step (expected vs. saw), or blocked, with screenshots, console errors and failed requests. It is evidence for QA, never the sign-off.
- It signs in with the environment's QA account, stored as two Secret Manager secrets — never on production.
- Each run has its own dollar budget, set in "Limits and rules" › "QA".
- A run that ends with failures files one bug work order and assigns it back to the developer.
- You can run it after every deploy outside production, or only when QA asks — and add it to the workflow as a "QA agent (browser)" step.