73 lines
3.2 KiB
Markdown
73 lines
3.2 KiB
Markdown
# Google Play closed-test runbook
|
||
|
||
The developer account is a new personal account. Google currently requires at
|
||
least 12 testers to remain opted in to the closed test for 14 continuous days
|
||
before production access can be requested.
|
||
|
||
## Before inviting testers
|
||
|
||
1. Complete Play developer identity and contact verification.
|
||
2. Create the Play app with package `org.whoneedhelp.mobile`.
|
||
3. Enable Play App Signing.
|
||
4. Add the Play App Signing SHA-256 fingerprint to production App Links and
|
||
Google/Firebase configuration, then verify the production association files.
|
||
5. Upload the source-bound production AAB.
|
||
6. Complete the store listing, App content, privacy, Data Safety, content rating,
|
||
ads, target-audience, and access declarations.
|
||
7. Start with an internal test on the owner’s device, then promote the verified
|
||
build to the closed track.
|
||
|
||
## Tester cohort
|
||
|
||
- Recruit at least 12 real people with Google or Google Workspace accounts.
|
||
- Keep at least 14 opted in so that one accidental opt-out does not reset the
|
||
minimum cohort; this is an operational buffer, not a Google requirement.
|
||
- Do not publish tester email addresses in the repository.
|
||
- Give every tester the Play opt-in link and state clearly that they must remain
|
||
opted in for at least 14 continuous days.
|
||
- Record opt-in date, device/Android version, completed scenarios, and feedback
|
||
in a private operational sheet.
|
||
|
||
## Required scenarios for each cohort
|
||
|
||
- Install and open from the Play closed-test listing.
|
||
- Register or sign in with Google/email.
|
||
- Review privacy and location controls.
|
||
- Create or browse a request without exposing an exact public address.
|
||
- Accept/withdraw from a safe test request using two separate accounts.
|
||
- Send and receive private messages and push notifications.
|
||
- Start and stop live location on a clearly labelled synthetic test assignment.
|
||
- Request to join and withdraw from an activity.
|
||
- Block/report a synthetic account and locate support/account deletion.
|
||
- Confirm that rotation, background/foreground, offline/reconnect, and process
|
||
recreation do not lose critical state.
|
||
|
||
Never ask testers to simulate a real emergency, disclose prescriptions or
|
||
medical details, exchange money, or travel to meet an unknown person.
|
||
|
||
## Feedback questions
|
||
|
||
1. What task did you try to complete?
|
||
2. At which screen did you hesitate or stop?
|
||
3. Was approximate versus exact location visibility understandable?
|
||
4. Did notifications arrive, and did they open the expected screen?
|
||
5. Could you tell when live location was active and stop it?
|
||
6. Did leaving a request/activity immediately update your participation state?
|
||
7. What device and Android version did you use?
|
||
8. Did you encounter a crash, blank screen, inaccessible control, or misleading
|
||
status?
|
||
|
||
## Evidence for production-access application
|
||
|
||
- Closed-track name and release/version code.
|
||
- Dates covering at least the required continuous 14-day interval.
|
||
- Opted-in tester count shown by Play Console.
|
||
- Device/Android coverage.
|
||
- Issues found, fixes made, and how fixes were re-tested.
|
||
- Summary of feedback and why the app is ready for production.
|
||
|
||
Official references:
|
||
|
||
- https://support.google.com/googleplay/android-developer/answer/14151465
|
||
- https://support.google.com/googleplay/android-developer/answer/9845334
|