Book a free call
What we testHow it worksSample reportPricingFree app checkBook a free call

QA testing for apps built with AI

It looks finished.Look closer.

Move the lens over this app. That is what we do to yours.

Bugs spotted 0/4Move the lens to find what is broken.

Illustration: a billing dashboard that looks fine. Under an X-ray lens it shows four bugs: an API that answers without login, another company's invoices visible, a live secret key in the JavaScript, and a payment webhook that credits twice.

We test apps built with

  • Cursor
  • Lovable
  • Bolt
  • v0
  • Replit
  • Claude Code
  • Windsurf
  • GitHub Copilot
  • Supabase
  • Firebase
  • Stripe
  • Next.js

The problem

AI builds what you ask for. Nobody tests what you didn't.

Every fix can quietly break something else.

  1. youLogin is broken again. Users land on a blank page.
  2. aiYou're absolutely right! I've fixed the login redirect.Updated 3 files
  3. youLogin works. Now checkout shows an error.
  4. aiApologies for the confusion! I've rewritten the checkout session.Updated 14 files
  5. youLogin is broken again.

What security researchers found in AI-built apps

5,000

AI-built public apps exposing sensitive company data, out of about 380,000 scanned.

Red Access, via Axios (2026)
45%

of AI-generated code samples had a security flaw, across 100+ models.

Veracode GenAI Code Security Report (2025)
400+

exposed secrets and 2,000+ vulnerabilities in 5,600 vibe-coded apps.

Escape.tech (2025)
6 → 35

CVEs a month traced to AI-written code, January to March 2026.

Georgia Tech SSLab, Vibe Security Radar

Six things that break in AI-built apps.

Pick one to see what your users would see.

yourapp.com/adminNot signed in
PPriyaOwner
MMarcoDeleted
> fetch("/api/users/42", { method: "DELETE" })200 OK

The button is hidden, the route is not. Call the API or open /admin directly and it answers, signed in or not.

We call every route and API directly: signed out, and as the wrong user.

Your app, ready to test

Illustration: a QA pass over an app finds three bugs, in the database, webhooks and profile page, which are then fixed and covered by tests.

Press the button for the ten-second version.

How it works

From call to report in five days.

  1. Day 0

    20-minute call

    Scope and fixed price, in writing.

  2. Day 1

    Access

    A URL and two test accounts. No code needed.

  3. Days 1-4

    Testing

    Real browsers and phones, as a customer and as an attacker.

  4. Day 5

    Report

    Every bug with steps, screenshot and a fix prompt.

  5. After

    Safety Net

    Optional Playwright tests on every push.

What did you build it with?

Every tool cuts corners somewhere. This is where we look first.

Lovable

Supabase row-level security, what the public key can reach, edge function auth.

Bolt

Secrets in the browser, missing server-side validation, direct API calls.

Cursor

Multi-file edits that quietly break other flows. We add regression tests.

Claude Code

Large refactors. We check every critical flow still works afterwards.

v0

Empty, loading and error states, forms, accessibility and mobile.

Replit

Secrets handling, auth on every route, behaviour with real data.

Firebase

Security rules: reads and writes across accounts and by signed-out users.

A report you can act on the same day.

Launch Check report · acme-billing.app

Not ready to launch yet. Two critical fixes first.

2 critical2 high1 low31 passed

IDSeverityFinding
QA-0412CriticalAny signed-in user can read every customer's invoices
QA-0415CriticalStripe webhook retry grants credits a second time
QA-0409HighPassword reset link still works after it has been used
QA-0418HighProfile page crashes when the bio field is empty
QA-0421LowSignup button cut off on iPhone SE
QA-0403PassLogin, logout and session expiry on 4 browsers

Sample report. App name and findings are illustrative.

QA-0412 in full: every finding comes like this.

QA-0412CriticalOpenLaunch Check, day 2

Any signed-in user can read every customer's invoices

GET /rest/v1/invoices · Chrome 131, Safari iOS 18

Steps to reproduce

  1. Sign in as test user B
  2. Open the browser console
  3. Run supabase.from("invoices").select("*")

Expected

Only user B's invoices.

Actual

Invoices from every account.

Fix prompt for your AI tool
Enable row-level security on the "invoices" table in Supabase.
Add a SELECT policy so users can only read rows where user_id = auth.uid().
Add matching INSERT, UPDATE and DELETE policies.
Do not change any other table. Show me the SQL you ran.

Sample from a Launch Check report. App and account names replaced.

Pricing

Fixed prices, agreed in writing before we start.

Not sure which one you need? Start with a Launch Check. If we find nothing serious, you get that in writing too.

Start here

Launch Check

$490fixed

Before you launch, demo to investors or open signups.

  • Signup, login, payments and your core feature tested on real browsers and phones
  • Security basics: permissions, data access between users, exposed keys
  • Every bug ranked by risk, with steps to reproduce
  • A fix prompt per bug, ready to paste into Cursor, Lovable or Claude
  • A plain go / no-go summary you can share with your co-founder

Takes 3-5 days.

Book a Launch Check

Safety Net

from$1,500

When every new prompt might break something that worked yesterday.

  • Playwright tests for the flows that make you money
  • Runs in GitHub Actions on every push and pull request
  • Readable reports with screenshots and traces when something fails

Takes 1-3 weeks.

Ask about Safety Net

QA Partner

from$990/ month

For teams shipping weekly without a QA engineer.

  • Release checks before each deploy
  • Test suite kept green as the app changes
  • Scope, volume and response times agreed in writing

Billed monthly.

Ask about QA Partner

Testers who know how software breaks.

14+

years of software testing, for companies in

  • Australia
  • United States
  • United Kingdom
  • Finland
  • Japan

QA specialists

Testers, not developers marking their own work.

Fix prompts

Paste-ready for Cursor, Lovable or Claude.

No code access

A URL and two test accounts to start.

Fixed price

Scope and cost in writing first.

A real team

More testers when the release is bigger.

NDA on request

Test data deleted when we finish.

What we do

  • Exploratory testing
  • Playwright automation
  • API testing
  • Security basics (OWASP)
  • Cross-browser and mobile
  • CI with GitHub Actions

Common questions.

Something else on your mind? Write to hello@qabasic.com.

Do you need access to our code?

Not for a Launch Check. We test the running app from the outside, the way users and attackers see it. A URL and test accounts are enough. For a Safety Net we work in your repository so the tests run in your CI.

Our app was built with Lovable, Bolt or Cursor. Is that a problem?

No, that is exactly who we work with. The tool does not matter much, because we test behaviour, not style. We do know where each stack tends to cut corners, such as Supabase row-level security or unprotected API routes.

Will you fix the bugs as well?

Every bug comes with reproduction steps and a fix prompt you can paste into your AI tool. If you would rather we fix them, we can scope that separately.

Why not just ask the AI to write tests?

AI-written tests usually confirm the code it just wrote, with the same blind spots. We test from the outside with the intent to break things, and we check that every test fails when it should.

How long does a Launch Check take?

Three to five working days from the day we get access. You get the report and a walkthrough call at the end.

Who owns the tests you write?

You do. Safety Net tests live in your own repository and run in your own CI. If you stop working with us, they keep running.

How much does it cost?

A Launch Check is $490, fixed. A Safety Net starts at $1,500 and QA Partner at $990 a month, depending on how many flows your app has. Either way you get a fixed price in writing before we start, within one business day of a short call.

Will you sign an NDA?

Yes. We are happy to sign yours before we see anything, and test data is deleted when the engagement ends.

Tell us about your app.

  1. We reply within one business day to pick a time.
  2. A 20-minute call about your app, your stack and what worries you.
  3. A written scope and fixed quote. No obligation.

Prefer email? hello@qabasic.com

We only use your details to reply.
0bugs eliminated