AppReviewX Log in

Test environment setup checklist

Staging data, accounts, feature flags and monitoring to prepare before you invite testers. Every item with its reason and how to check.

updated ·3 min read

In this guide

Testers lose their first session when the backend is down, the test account does not work or the app points at the wrong server. Run this list before you send any invite. Each item has a reason and a way to verify it.

# Item Why How to check
1 The build points at the test backend, not production Test actions must not touch real users or real money Check the base URL in the installed build; make one action and look for it in the test database
2 Test backend is up and reachable from outside your network Testers are not on your Wi-Fi or VPN Open it from mobile data on a phone
3 Test accounts exist for each role (new user, regular, admin if relevant) Testers should not waste time registering or guessing Log in with each from a clean install
4 Credentials are in the invite, not only in your head Prevents the first support question Re-read the invite as if you were a stranger
5 Seed data is realistic (long names, empty and full lists, special characters) Empty or tidy data hides layout and logic bugs Click through the main lists with this data
6 Data can be reset quickly After a bad test run you need a clean state Run your reset once and time it
7 Payments and emails run in sandbox/test mode No real charges or mails to real addresses Make one test purchase; check where emails go
8 Feature flags are set for the build being tested Unfinished features should be hidden or marked List the flags and their values for this build
9 Third-party keys (maps, push, auth) are valid for the test build Keys tied to another app ID fail silently Trigger each service once on a device
10 Push notifications reach a test device Often misconfigured only in test builds Send one from the backend
11 Crash and error reporting is on, with the build number attached You will not get logs from testers otherwise Force one test crash and find it in the dashboard
12 Logging does not store passwords or personal data Test data can still be real people's data Read a sample of log lines
13 Testers can install the build (link, group or invite works) The most common first failure Install through the exact path testers will use, on a second device
14 The build number is visible in the app Every report needs a version Open settings or an about screen
15 A known-issues list exists Saves testers from reporting what you know Write it before the invite
16 There is one place to send feedback and you will see it Scattered feedback gets lost Send yourself a test report

Template: pre-invite readiness note

Environment: [staging URL]   Build: [number]   Date: [date]
Checked by: [name]
[ ] 1-16 above done. Exceptions: [list]
Known issues: [list]
Reset procedure: [steps]

Adapt it

Drop items that do not apply (no backend, no payments). Add anything specific to your stack, such as a database migration or a seeded demo mode. For how to test migrations, see the related checks on testing database migrations without losing data.

When the environment is ready, AppReviewX can supply private, structured feedback from testers. One feedback = 1 credit; new accounts start at 0. Start free.