Guide · updated 12 November 2026
How to test your app before launch
Most apps don't fail at launch because the idea was bad. They fail because nobody checked them end to end. This is how to do that with a small team, and a checklist you can copy.
We have built apps for founders who ended up frustrated, not with us, but because their app never launched. The team kept building, and building, and leaving potholes behind them, until the app wasn't usable. We did the same with our own apps. The fear was always “what if something breaks?”, and somehow the answer was always another feature.
Most small companies don't have a QA team. Not everyone has 500 people who can test everything for them. So the app gets clicked through, someone catches what they catch, and it ships. Measure five times and cut once is the old rule. This is the measuring part, in an order a small team can finish. (For the week-to-week routine after launch, see QA for startups.)
1. Stop adding features and write the list
Pick a date and freeze what goes in. Then write down every screen, form and journey that is in the app, with the result a user should see. One line per journey: what has to be true first, the steps, and the expected result. Without this list you only test what you remember building, and the parts you forgot are the ones that break.
If an AI wrote most of the code, have it write the list from the code. Our free test-checklist skill does this in Claude Code, Cursor or Codex, grouped by area, with a column for each platform (see how to test code written by Claude Code). For the format, the test plan template has a worked example.
2. Test the journeys people came for, on every platform
Start with sign-up, sign-in and password reset, then the one job the app exists to do, then payments and every email it sends. Do each on web, Android and iPhone if the app runs there. A fix that works in the browser often never reached the phone. Record a result per platform, not one tick per journey.
3. Test what happens when people don't go the way you expect
We usually test whether it works. We rarely test what happens when someone doesn't understand the app, or takes a path we never planned. Submit forms empty and wrong. Press Back and Refresh mid-way. Tap Pay twice. Cut the network. Open the admin pages as a normal user by typing the URL.
4. Hand it to a stranger and keep quiet
Give the app to two or three people who have never seen it, ask them to do the main job, and watch without helping. Every place they stop is a bug, even if the code is doing exactly what you wrote. This takes an afternoon and finds more than a week of testing your own app.
5. Fix, then retest every fix
A fix only counts once someone repeats the original steps on the platform it was reported on and sees it work. Then check the screens around it, because fixes break neighbours. That is retesting and regression testing, and launch week needs both.
6. On launch day, test the live build
The build in the store and the site on your real domain are not the one you tested. Repeat sign-up and the main job on production, with live keys and the live database. Make sure errors reach you and that someone reads the help inbox. For phones, the mobile app testing checklist covers permissions, interruptions and updates; for every release after this one, use the release checklist.
The pre-launch checklist
Fourteen checks in three groups. Copy them, or import them and add your own app's journeys.
# Before launch: checks for a new app ## The journeys people came for (CORE) | ID | Journey | Preconditions | Steps | Expected result | WEB | AND | IOS | |---|---|---|---|---|---|---|---| | CORE-01 | Sign up as a stranger would | A new email address, no account | 1. Open the app from its public link or store page. 2. Create an account. 3. Confirm the email. | The account works, the email arrives within a minute, and the first screen says what to do next. | | | | | CORE-02 | Sign in, sign out, reset a password | An existing account | 1. Sign out. 2. Sign in. 3. Use Forgot password and follow the email. | Each step works and the reset link signs you in with the new password. | | | | | CORE-03 | The one thing the app is for | A new account | 1. Do the main job of the app from start to finish (book, post, pay, invite). | It completes, the result is saved, and it is still there after a reload. | | | | | CORE-04 | Payment, if the app takes money | A live card, the lowest price | 1. Pay for real. 2. Check the receipt. 3. Refund it. | The charge, the receipt and the refund all show up where they should. | | | | | CORE-05 | The emails and notifications | A new account | 1. Trigger every email and push the app sends. | Each one arrives, reads correctly, and its link opens the right screen. | | | | ## Paths nobody planned for (EDGE) | ID | Journey | Preconditions | Steps | Expected result | WEB | AND | IOS | |---|---|---|---|---|---|---|---| | EDGE-01 | Someone who doesn't read the instructions | A new account, no help | 1. Hand the app to someone who has never seen it. 2. Watch without helping. | They finish the main job. Write down every place they stop. | | | | | EDGE-02 | Empty and wrong input | Every form | 1. Submit it empty. 2. Submit wrong formats and very long text. | A clear message beside the field. Nothing saved half-way. | | | | | EDGE-03 | Back, refresh and tapping twice | Mid-way through the main job | 1. Press Back. 2. Refresh. 3. Tap Save or Pay twice. | No duplicate records, no lost data, no stuck screens. | | | | | EDGE-04 | A slow connection, then none | Network throttled, then cut | 1. Repeat the main job. | A loading state, then a clear error. It recovers when the network returns. | | | | | EDGE-05 | The wrong role | A normal account | 1. Open admin screens and other people's records by URL. | Refused, on the server as well as in the menu. | | | | ## Launch day (LIVE) | ID | Journey | Preconditions | Steps | Expected result | WEB | AND | IOS | |---|---|---|---|---|---|---|---| | LIVE-01 | The live build, not the test one | The production app or store build | 1. Repeat CORE-01 and CORE-03 on production. | Both work with live keys, the live database and the live domain. | | | | | LIVE-02 | The smallest screen and an old phone | The smallest supported phone or a narrow browser | 1. Open every main screen. | Nothing overlaps or is cut off, and every button can be tapped. | | | | | LIVE-03 | Errors reach you | Error reporting set up | 1. Cause a harmless error on purpose. | It shows up in your error reports or inbox within minutes. | | | | | LIVE-04 | Someone can reach you | The app's help or contact link | 1. Send a message through it. | It arrives somewhere a person reads every day. | | | |
Or take the file: Markdown·CSV·Excel·no email, no sign-up.
Know when it is ready
In qarunbook the checklist becomes a board with a result per platform. Testers record what they see and raise issues against a check; developers, or Claude Code over our QA MCP server, fix them and send them back for a retest. You can see how many checks have passed on each platform, so “is it ready to launch?” has a number for an answer instead of a feeling. One person and one app are free.