Start a project

A QA checklist for apps built with AI tools

4 min read

Built your app with Cursor, Lovable, Bolt, Replit or a chat assistant? Run this checklist before you launch. It covers sign-in, data, payments, devices and what to recheck after every change.

Hands typing on a laptop with code on screen, a coffee cup beside it, while testing an app

This checklist is for people who built an app with an AI tool and want to know whether it is safe to put in front of customers. You do not need to read code to use it. You need the app, two test accounts, a phone, and about two hours.

Work through it in order. Write down everything that surprises you, even if you are not sure it is a bug.

Before you start

  • Create two ordinary accounts, A and B, with different email addresses.
  • If the app has an admin role, keep that as a third account.
  • Use a test payment mode if your payment provider has one. Do not test with a real card on a live account.
  • Open the app in a private browser window, so you see what a new visitor sees.

1. Sign-up and sign-in

  • Sign up with an email that has a space before or after it.
  • Sign up with an address that is already registered. The message should not reveal more than it needs to.
  • Sign up with a one-letter password. Is it accepted?
  • Enter the wrong password ten times in a row. Does anything slow you down?
  • Ask for a password reset. Use the link, then try to use the same link again.
  • Sign out, then press the browser's Back button. You should not see private pages.
  • Sign in on a phone and a laptop at once, change the password on one, and check the other.

2. Other people's data

This section finds the most serious problems, and AI-built apps fail it often.

  • As user A, open something private: an order, a profile, an invoice. Copy the address from the browser.
  • Sign in as user B in another browser and paste that address. You should be refused.
  • If the address contains a number, such as /orders/1042, change it to 1041 and 1043.
  • As a normal user, type the address of an admin page.
  • While signed out, open pages that should need an account.

If any of these show you data, stop and fix that before anything else.

3. Every form

For each form in the app:

  • Submit it empty.
  • Fill every field with a very long text. Paste a full page of text into a name field.
  • Put letters where numbers go, and a negative number where a quantity goes.
  • Type <b>test</b> into a text field and look at where that text is shown afterwards. If it appears in bold, the app is not handling input safely.
  • Press the submit button twice, quickly. Did it create two records?
  • Fill the form, refresh the page, and see what is lost.

4. Payments and anything involving money

  • Compare the price on the page, the price at checkout, and the amount actually charged.
  • Apply a discount code, then remove an item. Is the total still right?
  • Use a card that will be declined. Is the order still created?
  • Start paying, then close the tab. Start paying, then press Back.
  • Pay successfully and check three things: the confirmation page, the email, and the record in your admin view. All three should agree.
  • Request a refund or cancellation and follow it to the end.

5. Phones and browsers

  • Open the app on a real iPhone and a real Android phone. An emulator on your laptop is not the same.
  • Turn the phone sideways.
  • Open the keyboard on every form. Can you still see the field you are typing in, and reach the submit button?
  • Switch to mobile data, or turn Wi-Fi off halfway through an action.
  • Try Safari, Chrome and Firefox on a desktop.
  • Zoom the page to 200%. Is anything cut off?

6. What the app sends and stores

  • Read every email the app sends, on a phone. Check the links in them.
  • Check that every page address starts with https.
  • Trigger an error on purpose, for example by opening a page address that does not exist. The page should not show code, file paths or database details.
  • Ask your AI tool directly: "Are any API keys or secrets included in the code that runs in the browser?" Then ask where each key is stored.

7. After every change

This is the step most solo builders skip, and it is where working apps get broken.

Each time you ask the AI to add or change something:

  • Test the new feature.
  • Then repeat sections 1, 2 and 4 of this list. They cover the parts that hurt most if they break.
  • Keep a short written list of your app's five most important actions, and run through it before every release.

If you find yourself releasing weekly, this manual rerun becomes slow. That is the point where automated tests start to pay for themselves.

What this checklist cannot do

It finds the common, visible problems, and for a small app that is most of them. It does not replace a tester who does this every day and knows where to look next when something seems slightly off. It also does not cover deeper security testing, which matters if you hold payments or personal data.

For the reasons behind each of these checks, read why apps built with AI need testing more than any other. And if you would rather have a second pair of eyes before launch, start a project and tell us what you have built.

Chat with us