QA testing runs
Compliance testing proves twelve people had your app installed. It says nothing about whether the app works. A QA run is the other thing: people using it on purpose, on devices you do not own, writing down what went wrong.
What a report contains
- Steps to reproduce. Numbered, in the order they did them — not “it crashed”.
- Device and version. Model and Android release on every finding, because half of all bugs are one device deep.
- Expected against actual. What they thought would happen, and what did.
- Severity. Blocker, major, minor or cosmetic, so you can plan rather than triage.
- A screenshot. Where a picture settles it.
You can brief them
If you want the sign-up flow hammered, or the payment sheet checked in Swahili, say so when you book. Testers work to the brief and then poke around freely, which is where the surprising findings come from.
Retests are included
Ship the fix and ask for a retest on the same findings. A bug marked fixed that is not fixed is worse than one nobody found, so we check rather than take your word for it.