GUIDE

Testing your app without writing tests

You'll never write automated tests, and that's fine. What catches launch-day failures in AI-built apps is not automated testing at all; it is half an hour of deliberately behaving like a stranger. Here's the script.

Be a stranger (10 minutes)

Open a private browser window. You are now a person who has never seen your app, with none of your logins and none of your assumptions.

Sign up with an email address you've never used here. Did the confirmation email arrive, and how fast? (If it didn't.)
Log out. Log back in.
Click "forgot password" and actually complete the reset.
Do the main thing your app is for, start to finish, without using anything you know as the owner.
Try to break it politely: submit an empty form, a wrong password, a silly-long name, an emoji, a made-up URL like /nonsense. It should say something helpful rather than showing a crash.

Be a stranger with a phone (10 minutes)

Same script, on your actual phone, on mobile data rather than your home wifi (that also proves the site works outside your network). Watch for: text too small, buttons you can't hit, anything cut off at the edges, forms that fight the keyboard, and how long the first screen takes to appear.

Be a second person (5 minutes)

If your app has accounts, this is the check that matters most. Create a second account and confirm it cannot see anything belonging to the first. Change an ID in the URL from one you own to one you don't and see whether the app stops you. Data leaking between users is the single most common serious flaw in prompt-built apps, and it's invisible until it's a headline. Our 20-minute security check covers testing it properly.

Check what people see before they click (5 minutes)

Paste your link into a message to yourself. Does a proper title and image appear, or a grey box?
Does the browser tab show a real name rather than "Vite App"?
Is there a favicon?
Do your keys stay private? Run the free scanner on the live URL.

Write it down once

Turn the list above into your own checklist, specific to your app, and rerun it before each meaningful update. It takes fifteen minutes the second time. Paste this to have your AI generate the first draft:

Write me a manual test checklist for this specific app, aimed at someone who doesn't code. List every user-facing flow the app supports, in the order a new user would hit them, with the exact steps to test each one and what a correct result looks like. Include the failure cases worth trying (empty forms, wrong password, a URL that doesn't exist, a second user's data). Keep it to one page I can work through in fifteen minutes.

Plyo is the home for AI-built projects — every version saved, one click to undo, one click to publish, plus a safety check, visitor counts and backups. Free to start: 3 projects, no card needed.

Give your project a home