# App beta test plan

App: [name]
Build/version: [exact build]
Platform and supported OS: [iOS/Android and versions]
Research owner: [team role]
Round dates: [start and end]
Decision this round should inform: [one release or product decision]

## 1. Choose a journey

Write the question before inviting testers. Example: Can a new user create a note and find it after restarting? Replace the example with your own user goal. A task such as "try everything" makes it hard to compare observations or decide what to repair.

Primary task: [what the user should accomplish]
Starting state: [fresh install, returning account, permission state]
Supported device coverage: [device/OS combinations to include]
Time commitment: [realistic estimate]
Known limitations: [unavailable features or expected beta behavior]

## 2. Prepare access safely

- [ ] Open the official store/beta link using an eligible tester account.
- [ ] Confirm the named build can install and launch.
- [ ] Provide dummy data and an approved test account when needed.
- [ ] Keep passwords and recovery codes out of shared reports.
- [ ] Use provider sandbox workflows for purchase testing.
- [ ] Tell testers which actions are outside this round.
- [ ] Explain who can see submitted evidence and when it will be removed.

Access link: [official distribution URL]
Access troubleshooting contact: [business support contact]
Sensitive areas excluded: [payments, personal uploads, production changes]

## 3. Give a neutral task

Invitation task: [describe the outcome without explaining every tap]
Observation prompts:
- What did you expect to happen?
- Where did you hesitate or need help?
- What happened after the task or restart?
- Can you reproduce the problem? Which steps matter?

Approval should depend on attempting the task and providing specific observations, including build and device context. A reproducible defect or blocked task can be useful evidence. Praise, a minimum star score and a public store review are not acceptance conditions.

## 4. Review the round

Report identifier: [pseudonymous ID]
Outcome: [completed / blocked / abandoned]
Expected result: [description]
Actual result: [description]
Evidence: [optional redacted screenshot or reproduction steps]
Owner decision: [fix, investigate, follow up or defer with reason]
Retest build and task: [exact follow-up]

Separate a tester's observation from your interpretation. Record uncertainty when a report does not reproduce. Do not treat one successful task as proof that every feature works.

Template by RateMyApp: https://ratemyapp.io/resources/app-testing-templates/
Free to copy and adapt for your team's private testing. No attribution required.