PR-Time Verification
PR-time verification is the practice of running automated tests at the moment a pull request is opened — before code review begins — so reviewers see verified, passing changes rather than guessing whether the change works. AI coding agents make this possible at scale by invoking the test layer themselves.
In one sentence
PR-time verification means the act of opening a pull request automatically triggers verification (smoke E2E, visual diff, type check, integration probe), and the PR description includes the verification result, so the reviewer sees a verified change rather than a hopeful one.
Why it matters now
In pre-agent workflows, verification often happened after PR open — engineer pushes, CI eventually runs, sometimes hours later. The reviewer had to either wait or review unverified code. With AI coding agents authoring 40+ PRs per week, "wait for CI" is not a viable bottleneck. PR-time verification removes the wait by making verification part of the PR-open transaction.
The agent-native pattern
The cleanest way to deliver PR-time verification is to have the AI coding agent invoke the testing layer before opening the PR:
- Agent finishes implementing change.
- Agent calls an agent-native QA tool over MCP to verify behavior in a real browser.
- Verification produces structured output (pass/fail, screenshot, trace).
- Agent opens PR only if verification passes — and includes verification artifacts in the PR description.
- Reviewer sees a verified change with evidence, not a hopeful one.
This is the loop described in agent-native autonomous QA.
What verification covers at PR-time
| Layer | What runs | Time budget |
|---|---|---|
| Smoke E2E | Golden path through the changed feature | <2 minutes |
| Visual diff | Screenshots vs baseline | <30 seconds |
| Type/lint | Static checks | <30 seconds |
| Targeted integration | Tests touching files in the diff | <2 minutes |
Comprehensive regression runs after merge — the PR-time tier is sized to be fast enough that the agent can wait for it.
What PR-time verification is not
- Not a replacement for full regression — it covers PR-relevant flows, not the whole suite.
- Not the same as pre-merge CI — pre-merge CI usually runs after PR open. PR-time verification runs during PR open.
- Not exclusive to agent-authored PRs — humans can manually trigger the same verification before opening a PR; AI agents make it the default.