Testing
Automate Repetition; Ask People to Judge the Experience
Choose a testing method based on the question you need answered.
On this page · 4 sections
At a glance
In plain English
- Use scripts for predictable checks
- Use people for interpretation
- Do not confuse automation with participation
Use scripts for predictable checks
A scripted check can repeatedly verify navigation, a known calculation, or a saved preference. It is useful when you already know the expected result. Keep these checks deterministic and maintain them when the product changes so passing automation continues to mean something.
Use people for interpretation
A person can explain why a confirmation message feels ambiguous or why they do not trust a permission request. Give them room to describe their thinking. A bot replaying taps cannot substitute for that judgement, even if the resulting interaction count looks impressive.
Do not confuse automation with participation
Keep automated test output labelled as automated. Document human observations separately, and never present simulated activity as independent user feedback. Combining the two methods makes investigations stronger when each answers a clearly stated question.
Sources
Official references used
- App testing requirements for new personal developer accounts (Google Play Console Help)
- Set up an open, closed, or internal test (Google Play Console Help)
Continue
Choose the next step
Related
Next pages to read
Need 12 testers for 14 days?
Start a managed Google Play closed-testing run with verified testers, opt-in monitoring, and a closeout report.