Verdicts
How AMI decides whether a test passed, failed or is flaky.
Every test case in a run ends with one verdict. AMI only reports a verdict once the Reporter agent has checked the evidence, so a single slow response or network blip never decides a run on its own.
Pass
The test reached its expected outcome on the first attempt and every assertion held. Passing tests still keep their log, so you can see what AMI did.
Fail
The test reached a state that contradicts its requirement. AMI files a defect with the failing step, the expected and actual result, and a severity.
Repro steps
Each failure includes numbered steps that reproduce it against the same build. Steps reference the requirement they come from, so reviewers can trace a defect back to the spec.
Flaky
The test passed and failed across retries of the same build. Flaky results never fail a pull request by themselves, but they are tracked so unstable tests do not hide real regressions.
Retries
AMI retries a failed test before it calls it flaky. Set how many retries a run allows in your config:
export default defineConfig({ report: { failOn: "critical", retries: 2 },})A test that only passes on retry usually points at a race condition or shared state. Treat flaky verdicts as defects to investigate.