Launching an app that has not been properly tested is like opening a restaurant without tasting the food. It might be fine. It might also fail in front of every customer on the first night. Real users find problems quickly, and they rarely report them politely. They leave.

No-code does not remove the need for testing. Because apps are quick to build and change, they are also quick to break. This checklist of 25 items covers what to test before launch, grouped so you can work through it systematically.

Before you start

• Test on a separate test version, never on the live app.
• Use realistic data: names with apostrophes, long text, large files, empty fields.
• Test with several accounts, one for each role.
• Write down what you test and what you find.

Core functionality

1. Every main user flow, from start to finish, as each type of user.
2. Sign-up, login, logout and password reset, including wrong passwords and expired links.
3. Forms, including required fields, wrong formats and very long entries.
4. Edit and delete actions, and what happens to linked data.
5. Search, filters and sorting with both small and large amounts of data.

Security and access

1. Two-account test: confirm one user cannot see another’s data, including by changing IDs in the address.
2. Role restrictions: log in as the lowest-permission role and try restricted actions.
3. Private keys: confirm none are exposed in the page or browser tools.
4. File access: confirm uploaded files cannot be opened by the wrong person.

Our security guide explains the principles behind these checks.

Money and messages

1. Payments in test mode: success, failure, declined cards and cancelled payments.
2. Refunds and subscription changes, if relevant.
3. Email notifications: content, links, sender and where they land. See the SPF, DKIM and DMARC basics for deliverability.
4. Automatic reminders and scheduled workflows run when they should and only once.

Integrations

1. Each connected service works with correct data.
2. Failure behaviour: what the user sees if an outside service is slow or unavailable.

Experience and performance

1. Phone, tablet and desktop, in landscape and portrait.
2. Major browsers your users will use.
3. Page speed with realistic amounts of data. See database design mistakes and workload units for what slows apps and raises costs.
4. Empty states, such as a new account with no data, which should guide rather than confuse.
5. Error messages, which should be clear and kind.

Operations and launch

1. Backups and a way to roll back if something goes wrong.
2. Analytics and event tracking are recording what you need.
3. Privacy notice, terms and consent are in place and linked.
4. Support route: a clear way for users to ask for help.
5. Launch plan: who monitors the first hours, and what you will do if a serious problem appears.

Who should test

Do not rely only on the person who built it. Builders unconsciously avoid the paths that break. Ask someone unfamiliar with the app to complete key tasks without help, and watch where they hesitate. A few real users in a small pilot will find problems that hours of internal testing miss.

How we approach launch

Testing is part of every build, and the checks above map to our four-step framework of Discover, Build, Launch and Iterate. See our process from discovery to launch and realistic build schedules. Support after launch is billed from $35 per hour with no retainers and no minimums.

Frequently asked questions

How long should testing take?

It depends on the size of the app, but plan for it explicitly. Squeezing it out of the schedule is a common cause of rough launches.

Do I need automated tests?

For a first release of a typical no-code app, careful manual testing with a checklist is usually enough. Complex products may justify more.

What if I find a serious bug right before launch?

Delay if it affects security, payments or data. Launching with a known serious problem costs far more than a short delay.

Can you review my app before launch?

Yes. Email us and we will tell you what to check or review it for you.