# Testing an app you built with AI: a guide for founders

> You built it with Claude Code, Cursor, Lovable or Bolt and it looks done. How to check it works for a stranger and keeps working after every change.

By Jason Nguyen, Founder, Testsy. Published 2026-11-21. https://testsy.dev/blog/test-an-app-you-built-with-ai/

## Done is not the same as working

Building with AI is fast enough that testing becomes the slow part, so it gets skipped. The cost shows up later: agencies that rescue AI-built apps describe the same failures again and again, from the [blank screen in production](https://dev.to/chalom_ellezam_5989bce65e/i-deployed-12-vibe-coded-apps-to-production-the-same-6-things-broke-every-single-time-341f) to the [fix that breaks something else](https://rockingtech.co.uk/blog/why-your-vibe-coded-app-keeps-breaking).

This guide collects what we have written for people building this way. Each post is about one problem, says why it happens, and gives a plain-language test you can run against your live address. Where we have a real run to show, the post links to it.

## 1. Check what the agent called done

- [Your coding agent said “done”. Here is what it did not check](https://testsy.dev/blog/your-coding-agent-said-done-what-it-did-not-check/)
- [It works in preview and breaks in production. Test the live address](https://testsy.dev/blog/works-in-preview-broken-in-production/)
- [Catch the blank white screen after a deploy](https://testsy.dev/blog/catch-a-blank-white-screen-after-deploy/)
- [Test a Lovable, Bolt or Replit app by its address, no code needed](https://testsy.dev/blog/test-a-lovable-bolt-or-replit-app-without-a-coding-agent/)

## 2. The flows that break for strangers

- [Sign-up email links to localhost? Catch it before your users do](https://testsy.dev/blog/sign-up-email-links-to-localhost/)
- [Test password reset from the email to the new password](https://testsy.dev/blog/test-password-reset-from-the-email-to-the-new-password/)
- [Saved, then gone after a refresh: test that your app really saves](https://testsy.dev/blog/saved-then-gone-after-a-refresh/)
- [Test that one user cannot see another user's data](https://testsy.dev/blog/test-that-one-user-cannot-see-another-users-data/)
- [Test email verification codes, the wrong code and the resend too](https://testsy.dev/blog/test-email-verification-codes-wrong-code-and-resend/)
- [Sign-up emails that stop arriving after launch](https://testsy.dev/blog/sign-up-emails-stopped-arriving-after-launch/)
- [Paid, but still on the free plan: test the Stripe webhook](https://testsy.dev/blog/paid-but-still-on-the-free-plan/)
- [Uploads that work for you and fail for your users](https://testsy.dev/blog/uploads-work-for-you-fail-for-your-users/)
- [Test your app as a brand-new user, not as yourself](https://testsy.dev/blog/test-your-app-as-a-brand-new-user/)
- [Test what users see when a request fails](https://testsy.dev/blog/test-what-users-see-when-a-request-fails/)
- [Sign in with Google works locally and fails in production](https://testsy.dev/blog/sign-in-with-google-works-locally-fails-in-production/)

## 3. Keep it working

- [Fix one bug without breaking another: one bug, one test](https://testsy.dev/blog/fix-one-bug-without-breaking-another/)
- [Ten tests to run before you share your AI-built app](https://testsy.dev/blog/pre-launch-checklist-for-an-app-built-with-ai/)
- [Write a test without writing code: steps, checks and values](https://testsy.dev/blog/write-a-test-without-writing-code/)

## 4. Let the agent test its own work

- [Turn a failed test into a fix prompt for your coding agent](https://testsy.dev/blog/copy-the-fix-prompt-into-your-coding-agent/)
- [Make Claude Code test what it just built](https://testsy.dev/blog/make-claude-code-test-what-it-built/)
- [Let Cursor check its own work in a real browser](https://testsy.dev/blog/let-cursor-check-its-own-work-in-a-browser/)
- [Let Codex check its own work in a real browser](https://testsy.dev/blog/let-codex-check-its-own-work-in-a-browser/)
- [Test from Gemini CLI, the Claude desktop app and claude.ai](https://testsy.dev/blog/connect-testsy-to-gemini-cli-and-the-claude-app/)

## 5. Know the limits

- [What an AI tester cannot check for you](https://testsy.dev/blog/what-an-ai-tester-cannot-check-for-you/)

## The proof behind the posts

A post that says Testsy can do something should show it doing it. The runs linked from these posts are real runs on our practice site, with their results, replays and videos, open to anyone until 18 February 2027. The one in the picture at the top is a planted bug: an export that said it had started and downloaded an error page instead of a CSV. The tester opened the file and failed the check, in 40 seconds ([the run](https://app.testsy.dev/share/icyxfbiPb8jWKwJwiujZbNadQGVATj6D)).

## Start with one test

Paste your app's address into **New test**, describe sign-up and one thing your app saves, and run it. The free trial has 10 runs and needs no card.
