The diff lies
Review looks at the change. QA looks at behavior. A “correct” PR can leave checkout red and the acceptance criterion green.
AURA QA · UNDER CONSTRUCTION · NO DATE
Review says the diff looks good. QA proves it behaves.
The fifth step of the cycle — and the Achilles heel of agent-written code. Test against the spec, not against intuition. We are not selling it yet. There is no date.
Under construction · No billing or launch date · The cycle already closes today with Review
Step 05 · Test Under construction
Reviewthe diff passes
QAthe product behaves
- 01Criteria → casesThe spec stops being footer text on the PR
- 02Neighbor regressionLooks at the product, not only the diff
- 03Evidence for the reportWhat was tested, against what, with what result
We prefer not to date what we do not yet use ourselves every day.
Why it is the Achilles heel
The agent can fulfill the ticket and break what already worked.
The spec stays in the comment
Acceptance criteria are useless if nobody runs them. QA turns the spec into cases, not footer text on the PR.
Factories live on this
The client does not buy a merge. They buy that the product does what they asked. Without test evidence, the factory delivers opinion.
Test against the spec, not against intuition.
What it will do
Three acts. None has a date.
01Vision
The spec as oracle
Spec criteria become cases that someone — or something — runs against the change.
02Vision
Neighbor regression
The agent fulfills AURA-118 and breaks the coupon flow. QA looks at the product, not only the diff.
03Vision
Evidence for the report
What was tested, against which criterion, with what result. The same language as Review. For the CTO and for the factory's client.
No filler in the table
Independent module
QA will not “come included” in a plan to fill the table. When it exists, it will have its own price. Until then there is no row to sell and no date to miss. Review already verifies intent, coherence, quality, and security on every Pull Request.
Factories
Want QA only?
Some software factories do not need Spec or Orchestra: they need evidence that what they delivered behaves. Tell us how you test today. There is no waitlist with a date. There is a conversation to build this with people who will actually use it.
- No spam and no date promise
- A conversation to understand the case
- The cycle already closes today with Review