In this guide
Most weak feedback comes from the same few habits. Each has a quick fix.
1. Vague reports
"It does not work" or "the app is slow" gives the developer nothing to act on. Fix: say what you did, what you expected and what happened.
2. No device or version
A bug on one phone or OS version may not exist on another. Fix: always add device, OS version and app version.
3. Testing only the happy path
Sign up, tap the main button, done. Real users do more. Fix: also try empty fields, wrong input, going back, rotating the device, switching apps, losing the network.
4. Several problems in one note
The developer cannot track or answer a block of mixed issues. Fix: one problem per item, each with its own steps.
5. Missing steps
"Crashes on the profile page" does not tell how to get there. Fix: start steps from a fresh launch, numbered.
6. Mixing facts and opinions
"The button is cut off" is a fact. "I hate this color" is taste. Fix: label opinions as opinions and keep them separate.
7. Giving up after the first bug
One crash does not mean the rest is untested. Fix: note it, retry once, move on. See When an app crashes while you test it.
8. Copying text
Pasted generic text or text copied from the store page says nothing about the app you actually used. Fix: write from your own session, even if short.
9. Sharing private data
Screenshots can show your name, email or other people's messages. Fix: check before attaching. See Screenshot tips for testers.
10. Mixing feedback with ratings
Private feedback goes to the developer. A public store rating is a separate, voluntary and unpaid choice, never part of a test. See Testing apps is not trading ratings.
Before you submit
- Could someone repeat this from my steps?
- Did I add device and version?
- Is it about this app and this session?
Back to Become an app beta tester. Related: Beta tester vs QA tester, Testing apps in a language you do not speak well.