How to interpret results
Aucert produces structured test results with confidence scores, severity classifications, and visual evidence. Here's how to read them.
Confidence scores
Every finding includes a confidence score between 0.0 and 1.0:
| Score range | Meaning | Action |
|---|---|---|
| 0.95 - 1.0 | Very high confidence | Almost certainly a real bug |
| 0.85 - 0.95 | High confidence | Likely a real bug, quick manual check recommended |
| 0.70 - 0.85 | Medium confidence | Possible issue, manual investigation needed |
| Below 0.70 | Low confidence | May be a false positive |
tip
Set your confidence_threshold to match your team's tolerance. Start at 0.85 and adjust based on false positive rates.
Severity levels
| Severity | Description |
|---|---|
| Critical | App crash, data loss, security vulnerability |
| High | Major feature broken, user flow blocked |
| Medium | UI issue, minor functional problem |
| Low | Cosmetic issue, minor UX concern |
Bug report structure
Each bug report includes:
- Title — One-line description of the issue
- Severity — Critical / High / Medium / Low
- Confidence — 0.0 to 1.0 score
- Screenshots — Visual evidence at each step
- Device context — Emulator configuration and OS version
- Reproduction steps — Exact actions to trigger the bug
What's next
- CLI commands — Check results with
aucert status - Configure project — Adjust thresholds