AppReviewX Log in

Bugs testers find in AI-built apps (and how to report them)

Failure patterns worth testing in apps built mostly by prompt, plus a report format you can paste straight into your coding assistant.

updated ·2 min read

In this guide

Any app can have bugs, however it was made. This page is about the kinds of failures worth looking for when you did not write each line yourself, and how a tester can describe them so you can fix them quickly. It makes no claim about how often anything fails.

Failure patterns to test for

  • Works on the happy path only. Everything works if you do what the prompt described. Try skipping a step, going back or repeating one.
  • Empty and error states. What does a list show with no data? What happens when a request fails? A blank screen is a bug even if nothing crashed.
  • State lost on rotation or return. Rotate the phone, switch apps, come back. Is the typed text still there?
  • Screens that look right on one phone. Small screens, large fonts and notches can hide buttons or cut text.
  • Permissions. Deny a permission and see whether the app explains or just stops.
  • Offline and slow network. Spinners that never end, silent failures, lost input.
  • Buttons that do nothing. A control that looks finished but is not connected to anything.
  • Login and sessions. Logging out, logging in on a second device, an expired session.
  • Leftover demo content. Sample data, test accounts, placeholder text.

What a useful report contains

A tester who writes "it crashed" gives you nothing to act on. Ask for:

  1. Device and OS version.
  2. App version / build.
  3. Steps, numbered, from a fresh start.
  4. Expected result.
  5. Actual result, with a screenshot or screen recording.
  6. How often it happens (every time, sometimes, once).

More in bug report template for app testers and how to give useful app feedback.

Turn a report into a prompt

Paste the report as it is, then add the context your assistant lacks:

Here is a bug report from a tester.
[paste report]

Relevant screen/file: [name]
Please explain the likely cause first, then propose the smallest change that fixes it.
Do not change unrelated behavior.

Then re-run the tester's exact steps yourself. A fix is only a fix when the steps no longer reproduce the problem, and when the steps you ran before still work.

Keep a list

One line per bug: report, status (open, fixed, retest), build number. Ask the tester to retest the fix.

Next step

AppReviewX gives you private, structured feedback with the fields above in mind. One feedback you write earns 1 credit; new accounts start at 0. Start free.

Related: Vibe coding hub, closed test for an AI-built app, standing out among many new apps.