Annual Defect Report 2026Download

Resources

See what a verified defect report looks like

Every defect Mobot reports is triaged and verified by a QA analyst before it reaches your team, with video, logs, and reproduction steps attached — so a red result is never something your engineers have to chase down first.

Verified defect report
P0MOB-2481

Promo deep link opens the home screen instead of the promotion

After tapping the “Holiday 20% off” push notification, the app launches but resolves the deep link to the home tab. Reproduced on 3 of 3 attempts. Not reproducible when the app is already in the foreground.

  1. 1Launch app from cold start
  2. 2Tap promo push notification
  3. 3Deep link resolves to promo screen
  4. 4Add promoted item to cart
Analyst note: Confirmed real defect. Universal link association resolves correctly; the in-app router drops thepromo_idparameter on cold start. Attached device log shows the handoff at 00:04.2.
Device
Pixel 8 · Android 15 · LTE
Evidence
Video (0:31) · 4 screenshots
Logs
Device log · network log · steps
Reviewed by
Mobot QA analyst · 07:52 ET
Open in Jira →Post to Slack →

Condensed illustration of a report card.

Open the full sample report

A complete, sanitized report from a real run: 41 steps, a verified P0 crash, device and OS details, and 90-day analytics. Printable to PDF.

Anatomy of a report

Forensic detail your team can hand straight to an engineer

No retriage required. Everything needed to reproduce, assign, and fix is in the report the moment it lands in Slack, Jira, or TestRail. How we validate every defect →

Analyst verdict

A QA analyst reproduced the failure and confirmed it is a real defect — not a flaky run, not a copy change.

Step-by-step reproduction

Every action the robot took, with pass/fail per step, so an engineer can reproduce it the first time.

Video of the failure

Captured on the physical device at the moment it happened, alongside screenshots for each step.

Device & network logs

Timestamped logs from the device and the network at the point of failure, attached to the report.

Exact configuration

Device, OS version, network conditions, build, and app state (cold start, backgrounded, foreground).

Baseline vs. actual

Side-by-side comparison against the established baseline for every step, in the Mobot platform.

Get a report on your own app

Tell us about your build. We'll run it on real devices and send back a verified defect report you can review with your team.