OOmnistu

Blog / Engineering Playbooks

Engineering Playbooks

How to test a mobile app before launch: a practical plan

Build a mobile launch test plan covering critical flows, supported devices, test data, failure cases, accessibility and regression checks.

OOmnistu
Reviewed 2026-11-16 · 5 min read

Testing is where launches are won or lost, and where budgets get cut first. This guide gives you a plan you can ask your team to follow and check.

Why not only tap through it by hand

Android's testing documentation (https://developer.android.com/training/testing/fundamentals) says you can test manually on different devices and emulators, change the system language and try to produce every user error. It also says manual testing scales poorly and regressions are easy to miss, while automated tests are faster, more repeatable and usually give earlier, more actionable feedback. Use both.

Four kinds of test, by subject (from the Android docs)

Subject The question it answers
Functional Does the app do what it should?
Performance Does it do it quickly and efficiently?
Accessibility Does it work with accessibility services?
Compatibility Does it work on every device and OS version you support?

Three sizes of test, by scope

The same page distinguishes where tests run: instrumented tests run on a real or emulated device, usually UI tests; local tests run on a development machine or server and are usually small and fast. It also warns that code which is hard to test in isolation leads to bigger, slower, flakier tests and fewer scenarios covered.

Where to run each test: Android's testing strategy page

A second Android page, "Testing strategies" (https://developer.android.com/training/testing/fundamentals/strategies, read 15 Nov 2026), adds:

Two more Android pages describe where tests live: local unit tests run on your workstation's JVM, quickly but without the Android framework (https://developer.android.com/training/testing/local-tests); instrumented tests run on a physical or emulated device with more fidelity but much more slowly, and the page recommends them only when you must test against real device behaviour (https://developer.android.com/training/testing/instrumented-tests). Both pages were read in part for their setup sections.

A launch test plan (our template)

  1. Decide the critical flows. For a delivery app: sign up, search, add to cart, pay, track, cancel. Write them as numbered steps.
  2. Define pass/fail for each flow. Example: "A new user can place an order in under 2 minutes with no error."
  3. Pick the device matrix. List the oldest OS version you will support, one mid-range phone, one small screen and one large screen. Base the list on your own expected audience, not a generic one.
  4. Use test data only. Run payment and order tests in a sandbox or test mode with test payment methods and test accounts. Never use real customers' orders, cards or personal data to test. Confirm the test environment cannot reach real payment accounts, and clear test data afterwards.
  5. Test the unhappy paths. Airplane mode mid-checkout. Wrong card. App killed during payment. Denied permissions. Phone language changed.
  6. Run accessibility checks. Larger text, a screen reader, sufficient contrast.
  7. Run a performance pass. Cold start, a slow network, a long list.
  8. Automate the critical flows so they run before every release.
  9. Hold a release gate. Nothing ships with an open failure on a critical flow.

A tracking table you can copy

Flow Device/OS Result Defect ID Retested
Place order oldest supported OS
Place order small screen
Pay with failed test card (sandbox) mid-range phone

What to ask your development team

Limits

The testing taxonomy and strategy come from Android's documentation; iOS has its own tools, which we did not read (Apple's testing page did not load for us). We did not benchmark any testing tool. The plan template is our practical guidance, not a standard.

By Omnistu.

Sources

Previous
Mobile app security testing: what to expect and what to ask for