Regression test cycle (hired QA agent)
Regression runs on every release candidate, new bugs are filed with evidence, a coverage report is written; the “go” decision stays with the release manager.
Regression test cycle (hired QA agent)
- RC 2.14.0-rc3: 23 commits, changed areas payments, profile, notifications
- 412 tests selected (full regression), 9 new scenarios derived from acceptance criteria
- Run on 3 browsers + 4 devices: 409 passed, 3 failed; 2 passed on retry (flaky)
- Remaining failure consistent: payment summary rounding difference (0.01)
- BUG-2291 filed: steps, screen recording, logs; priority high, assigned to the payments team
- Report: coverage 91%, 2 flaky tests quarantined, escaped defects 0 (previous release 1)
- Release manager: “no-go” until BUG-2291 is fixed; re-run scheduled for rc4
- Work log: 412 tests · 1 bug · 9 new scenarios · hour-equivalent 11 · quality 4.8
- Report link and next run time sent to the team
- ■completed
Simulation · derived from real agent definitions · every agent can be built by dialogue with the Autonomous Agent and validated with a test corpus
Release-candidate tag from CI
Regression result, filed bugs and coverage report on the release record; work log updated
Agents
QA Supervisor
Decomposes the objective, delegates to agents, manages approval points, merges the result.
Test Plan Agent
Selects and extends the test set by changed areas
get_release_diffselect_testsgenerate_casesExecution Agent
Runs the tests, isolates flaky ones
run_playwrightrun_xcuitestretry_flakycollect_artifactsDefect Agent
Files bugs with evidence and steps, writes the report
file_bugwrite_reportlog_workSteps
| # | Kind | Agent | What happens | System | ms | tok |
|---|---|---|---|---|---|---|
| 01 | ingest | QA Supervisor | RC 2.14.0-rc3: 23 commits, changed areas payments, profile, notifications | CI/CD | 200 | — |
| 02 | reason | Test Plan Agent | 412 tests selected (full regression), 9 new scenarios derived from acceptance criteria | — | 900 | 1,300 |
| 03 | tool | Execution Agent | Run on 3 browsers + 4 devices: 409 passed, 3 failed; 2 passed on retry (flaky) | Device / Browser Grid | 1,800 | — |
| 04 | verify | Execution Agent | Remaining failure consistent: payment summary rounding difference (0.01) | — | 520 | 380 |
| 05 | write | Defect Agent | BUG-2291 filed: steps, screen recording, logs; priority high, assigned to the payments team | Jira / Xray | 520 | — |
| 06 | reason | Defect Agent | Report: coverage 91%, 2 flaky tests quarantined, escaped defects 0 (previous release 1) | — | 700 | 640 |
| 07 | approval | QA Supervisor | Release manager: “no-go” until BUG-2291 is fixed; re-run scheduled for rc4 | — | 2,600 | — |
| 08 | write | Defect Agent | Work log: 412 tests · 1 bug · 9 new scenarios · hour-equivalent 11 · quality 4.8 | Workforce Work Log | 300 | — |
| 09 | notify | Defect Agent | Report link and next run time sent to the team | Jira / Xray | 240 | — |
Feature delivery pipeline
A Jira epic turns into criteria, design, code and tests via agents; humans only review and approve the PR.
CI/CD release pipeline
Build, tests, scans and staging run unattended; production ships only on release-manager approval, via ArgoCD.
Incident response and hotfix
Alert fires, bug reproduced, patch and regression run ready; on-call approves, post-mortem already drafted.
Time to move from experimenting with AI to transforming with it.
In a 30-minute discovery session we take your 2–3 priority business problems, show a live demo of a similar scenario, and draft a roadmap that starts with the Value layer.
- Your 2–3 priority problems
- Live demo of a similar scenario
- Roadmap starting with value analysis