# Test the important paths

> Check your mobile app’s main tasks, accounts, connected services and small-screen behavior before release.

Canonical: https://www.rnblocks.dev/docs/testing-your-app
Updated: 2026-10-01

Test what a person can actually finish. A good-looking first screen is only the start.

## Use a short repeatable checklist

Section: https://www.rnblocks.dev/docs/testing-your-app#checklist

- First launch: does the app explain what to do when there is no data?
- Navigation: can you open a detail, go back and reach each main screen?
- Forms: try valid, missing and unusually long input; check the keyboard does not cover the action.
- Saved data: create an item, reopen the app and confirm it is still there when persistence is intended.
- Accounts: sign in and out. Check that a different account cannot see another person’s private data.
- Connected services: make one real request and check both success and failure states.
- Layout: test a small phone, a larger phone, both target platforms and larger text where supported.


## Give the agent a reproducible problem

Section: https://www.rnblocks.dev/docs/testing-your-app#report

> **A useful bug report**
> On iPhone, open Saved, tap the first destination and go back. The saved list becomes empty until I reload. It should keep the saved places. Please investigate this path and verify the fix.


## Test the release build too

Section: https://www.rnblocks.dev/docs/testing-your-app#release

Use a native test build for capabilities unavailable in the preview and before submitting. Test the same build and configuration intended for distribution, including authentication, connected features and support links.

- [Choose direct testing or a store testing track](https://www.rnblocks.dev/docs/publishing/testing)

## Continue

- [Choose a native preview](https://www.rnblocks.dev/docs/previewing-screens)
- [Prepare a release](https://www.rnblocks.dev/docs/publishing)
- [Troubleshoot a problem](https://www.rnblocks.dev/docs/troubleshooting)