Blue/green dev server
Builds deploy in containers and switch in only when the new version is healthy.
Automations · Automated QA
It tests what it shipped.
Done is not a merged PR. Done is a working product on a served version that the product owner accepts.
Live in productionPeaceMoney
BuildBuild 0.19.109 merged to devexample
illustrative
What is Automated QA in agnte?
Automated QA in agnte is a closed quality loop. Each build is deployed to a dev server in containers and switched in only when healthy (blue/green). Testers then check the API against its OpenAPI spec, read container logs for errors and restart loops, and re-test every fixed finding on the new version. Passing journeys become scripted tests that run without tokens.
Capabilities
What Automated QA does
PeaceMoney
API contract tester
Calls the API against its own OpenAPI spec with Schemathesis on every deploy.
Logs tester
Reads container logs after each deploy for errors and restart loops.
Product journeys gate
An MVP counts as done only when the user journey passes on the served version and the PO accepts it.
Re-test on every deploy
Fixed findings are re-tested on the new version; a failure reopens them.
Scenario catalog
Passing journeys become scripted tests that run without spending tokens.
Proof from production
Running today, measured.
73,501test results stored
659findings fixed and verified
Source: Live agnte database, 2026-10-12.
How it works
How Automated QA works
- Deploy blue/green
- Contract and log tests
- Findings to owners
- Re-test on next deploy
FAQ
Questions about Automated QA
Does agnte test the deployed app or just the code?
The deployed app. Builds go to a dev server and are tested on the served version.
What is the product journeys gate?
A rule that a milestone is done only when its user journey passes on the served version and the product owner accepts it.
Do repeat tests cost tokens?
Passing journeys become scripted tests in the scenario catalog and run without tokens.
Related