SAMPLE REPORT

Mobile app

The report below comes from testing the iOS and Android builds of a booking app.

Cases tested: 440
Total findings: 34
Release blockers: 3

Test summary

440 cases were tested on 14 real devices over five business days. 34 findings were reported; 3 would have blocked the store release.

Cases tested: 440
Total findings: 34
Release blockers: 3
Closed on re-test: 31

Severity distribution

3Critical

11High

14Medium

6Low

CLIENT: Anonymous · travel and booking
PACKAGE: Release
DATES: 3–9 February 2026
ENVIRONMENT: iOS 26 · Android 14–16 · 14 devices

Coverage matrix

Each square is one device-scenario pair. Coloured squares carry findings; click one to open it.

PassedCriticalHighMediumLow

Finding cards

Five of the 38 findings in the report. Each card is exactly the format you'll see in yours.

4 / 4 showing

CriticalCNRY-208Bookingandroid 14 · 3 GB RAM · low memory

The basket empties when the app returns from the background

Steps to reproduce

Pick a booking and reach the payment step.
Send the app to the background and open the camera.
Open a few more apps to create memory pressure.
Return to the app.

Expected: The selection survives and the user continues from the same step.
Actual: The app restarts and the basket is empty; the user starts over.
Impact: Directly raises booking abandonment on low-memory devices. Reproduced 5/5.
Evidence: video-208.mp4 · logcat-208.txt

CriticalCNRY-214Sign-inios 26 · iphone 15 · face id

Cancelling biometric sign-in still opens the session

Steps to reproduce

Close and reopen the app.
Tap “Cancel” at the Face ID prompt.
Check the home screen and the account page.

Expected: Without authentication the user stays on the sign-in screen.
Actual: The session opens; account details and saved cards are visible.
Impact: Anyone holding the device reaches the account without authenticating. Payment details are exposed.
Evidence: video-214.mp4

HighCNRY-221Paymentandroid 15 · throttled 3G

On a weak connection the payment request is sent twice

Steps to reproduce

Throttle the network to “Slow 3G”.
Reach the payment step and tap “Confirm”.
Tap again 3 seconds later while no response has arrived.
Open the booking list.

Expected: The second request is ignored and one booking is created.
Actual: Two bookings are created and the card is charged twice.
Impact: Direct financial impact and manual refund work. The button never locks until the response lands.
Evidence: video-221.mp4 · har-221.json

MediumCNRY-236First launchios 26 · clean install

Declining notifications freezes the app on first launch

Steps to reproduce

Install and open the app for the first time.
Choose “Don’t Allow” at the notification prompt.
Try to move past the welcome screen.

Expected: Onboarding continues whether or not permission is granted.
Actual: The welcome screen never advances; the “Next” button does not respond.
Impact: Users who decline notifications cannot use the app at all. Reproduced 4/4 on a clean install.
Evidence: video-236.mp4 · crash-236.log

The report keeps living after handover

The web report is a link, not a dead PDF. Its status updates as you mark fixes, and after the re-test round every finding's outcome shows up in the same place.

A report for another product type

Website and web applicationE-commerce, SaaS panels, corporate sites — anything that runs in a browser.Desktop applicationWindows and macOS, including install, update and offline behaviour.API and backend serviceREST and GraphQL: contract, permissions, boundaries and concurrency.

Don't test the next release alongside your users.

Start a test Read a sample report