Sign-up and e-mail confirmation
Sign up with an e-mail you have never used. Does the confirmation arrive, does its link open on a phone, can you sign in right after?
OFTEN: THE LINK LEADS TO LOCALHOST APP TESTING CHECKLIST
App testing checklist before launch.
To test an app before launch, go through it the way a new customer would: sign up, do the main action, pay with a test card, open every e-mail, try a second account and a real phone. These are 10 places where apps built with AI often break.
Bug testing — $299 for one platform. No bug found — 100% back.See a sample reportTHE CHECKLIST10 checks.
10 checks.
Before your customers.
Use a new e-mail and a phone you did not build on. Write down every step that surprised you — it may be a bug.
01 / SIGN-UP 02 / LOGIN Login, logout and password reset
Sign out, sign in again, reset the password from the e-mail. Enter a wrong password a few times: is the message clear?
OFTEN: THE RESET LINK OPENS THE PREVIEW03 / MAIN ACTION The main action, end to end
Do what the app exists for — an order, a booking, a generation — to the very end. Refresh the page: is the result still there?
OFTEN: THE RESULT VANISHES ON REFRESH04 / PAYMENT Payment with a test card
In your payment provider’s test mode, pay, press “Pay” twice, close the payment page halfway and come back. Does access open exactly once?
OFTEN: PAID, BUT NO ACCESS05 / E-MAILS Every e-mail the app sends
Welcome, receipt, password reset: open each one. Check the sender, the links, the language and the spam folder.
OFTEN: LINKS TO THE TEST ADDRESS06 / ROLES A second account and roles
Create a second customer. Can it open the first one’s orders, files or profile? Can a customer open the admin page by its address?
OFTEN: ONE CUSTOMER SEES ANOTHER’S DATA07 / PHONE A real phone
Open the app on an iPhone (Safari) and an Android phone (Chrome): forms, the keyboard over buttons, sideways scrolling, menus.
OFTEN: THE BUTTON HIDES UNDER THE KEYBOARD08 / ERRORS Empty states and errors
Wrong input, an empty list, a file that is too big, no connection. Does the app say what went wrong and what to do?
OFTEN: A SPINNER THAT NEVER STOPS09 / LIVE The live address, not the preview
Test on your own domain with live settings: environment variables, redirect addresses in the login settings, payment webhooks.
OFTEN: WORKS IN THE PREVIEW ONLY10 / AFTER FIXES After every fix — the old flows again
An AI tool can change more than you asked. After each fix, repeat checks 1–4 before you ship.
OFTEN: ONE FIX BREAKS ANOTHER FLOW
WHY PEOPLEYou built it.
You built it.
That’s the catch.
The checklist helps, but whoever built the app takes the paths they know.
You know where to click
Your customers don’t. A person who has never seen the app finds the steps you skip without noticing.
AI tests in a browser
Lovable’s browser testing, for example, tests only pages without sign-in if your app uses its own Supabase project or another login provider, calls complex upload widgets, drag-and-drop and subtle visual details unreliable, and runs in a browser, not on a real phone.
This list — and more
Our QA engineer goes through up to 25 screens, all roles and a real computer and phone, and writes every bug with steps, a screenshot and an AI prompt.
PRICINGStart with a release.
Start with a release.
Take it from there.
Fixed prices. You see the total before you pay — nothing is charged without your decision.
THE WHOLE APP · UP TO 25 SCREENS
Bug testing
The first test of your app.
$299/ 1 platform
Order bug testing — $299 - The whole app — up to 25 screens or pages
- 5 main scenarios and all roles
- Real devices: computer and phone
- Test report: every bug with a screenshot and an AI prompt
- 14 days of retests
No bug found — 100% back
FOR APPS WITH PAYMENTS OR PERSONAL DATARECOMMENDED
Bugs + vulnerabilities
Bugs + break-in attempts, the way a hacker would.
- Everything in Bug testing
- Other people’s data and files
- Database access rules (Supabase, Firebase)
- Keys in the code, admin and APIs without login
- Forged payments and password guessing
No bug found — 100% back
SAVE UP TO $347
Testing subscription
For regular releases.
- 4 tests in 30 days: the first for bugs, then of your updates
- The whole app — up to 25 screens or pages
- 5 main scenarios and all roles
- Real devices: computer and phone
- A report for every test, plus retests of your fixes
No bug found — 100% back
Update testing — $149. For an app we have tested before. Order update testing ↗︎
Vulnerability testing — $349. Without bug testing. Order on its own ↗︎
Options. One more platform — +$149. 25 more screens — +$149. Rush report within 1–2 business days — +$99.
QUESTIONSFrequent
Frequent
questions.
Can I test my app myself?
Yes — this checklist is how. Use a new e-mail, a second account and a phone you did not build on. When the app takes payments or keeps personal data, have someone who did not build it go through it too.
Doesn’t my AI builder test the app already?
Partly. Lovable’s browser testing, for example, signs in only with Lovable’s built-in backend; with your own Supabase project or another login provider it tests only pages without sign-in. Its docs call complex upload widgets, drag-and-drop and subtle visual details unreliable, and it runs in a browser rather than on a real phone. It is a good quick check of what you or the AI decide to test.
What does piperlink test beyond this list?
Bug testing ($299 per platform): the whole app up to 25 screens or pages, 5 main scenarios, all roles (up to three), a real computer and phone. Every bug comes with priority, steps to reproduce, a screenshot and a ready AI prompt, and you get 14 days of retests. No bug found — 100% back.
How long does your testing take?
The test plan within 1 business day of payment, the report within 5 business days of the plan (a rush report in 1–2, +$99), then 14 days of retests of your fixes.