For developers

Structured QA without
the enterprise overhead.

Structured QA from verified human testers — custom report forms, device and browser requirements, screen recordings, and approve/reject on every submission.

Post your first test How it works

Free to join — pay only when you post a test.

What's in a submission

Everything you need to
ship with confidence.

Every approved submission includes three things —
not just a bug report dump.

Screen recording

Every submission includes a screen recording — captured in-browser inside QATested, with an external link as a fallback. Watch playback in your dashboard, then export MP4 files with your submission data.

Structured answers

Testers answer the exact questions you define — not freeform paragraphs you have to interpret. You control the form: rating scales, multiple choice, free text, or a mix.

Export anywhere

Copy a spreadsheet-ready table, or download CSV, JSON, Markdown, or a ZIP with screenshots and recordings. Or send a finding straight to Jira, Linear, GitHub, or Slack — one-way into tools you already use.

How it works

From idea to feedback in a five-step flow.

No account manager. No procurement. No minimum spend. See each step in the interactive product tour →

1

Write your test instructions

Describe what your software does, what you want testers to explore, and any specific scenarios to run through. Be as detailed as you need — testers follow your instructions, not their own agenda.

  • Set the URL (web app, staging environment, mobile-friendly site)
  • Attach staging login credentials for auth-gated apps
  • Specify target devices and browsers
  • Set a deadline — typically 48–72 hours
2

Build your feedback form

Create a custom form so testers answer the questions that actually matter for your build. Use a built-in template for common QA scenarios, or build from scratch with free text, rating scales, and multiple choice fields.

3

Set your slot count and pay rate

Choose how many testers you want and how much each slot pays. Higher pay per slot attracts testers faster and lets you gate access to higher-tier testers (Rising, Top, Elite) who have stronger track records.

  • Minimum $5 per slot
  • 20% platform fee on top of tester pay
  • Unused slots are automatically refunded
4

Pay and publish

Sign up is free — you only pay when you post. Checkout via Stripe and your test goes live immediately — no waiting for approval, no account manager to phone. Testers who match your device requirements can see and claim slots right away.

5

Review submissions and approve

Submissions arrive in your dashboard as testers complete them. Watch the in-browser recording, read the answers, then approve or reject. Send a finding to Jira, Linear, GitHub, or Slack — or export CSV, JSON, or a ZIP when you're ready to share with your team.

  • Reject for incomplete or off-brief work — not hard findings on thorough submissions. Rejections are moderated; testers can see your reason
  • Approved submissions trigger automatic payout to the tester
  • Unused slots refund automatically after your review window closes
Form builder

Ask exactly the right questions.

Most QA feedback is useless because testers don't know what you need to know. QATested lets you build a structured feedback form testers must complete before submitting.

Use a built-in template for common scenarios — checkout flow, onboarding, cross-browser QA, mobile layout — or build your own with rating scales, multiple choice, and free text fields. Every tester answers the same questions, so you can compare responses side by side.

Need a head start? Describe your product or pain point in plain language — optional AI matches a starter template, tailors field wording to your app, and can review your draft brief before you publish.

Feedback form — Checkout flow
Yes, without any issues
Yes, but I hit a problem
No, I couldn't complete it
★★★★☆   4 / 5
The promo code field disappeared after I applied it — I wasn't sure if it had worked...
In beta WordPress sandbox

Real WordPress. Real testers. No staging setup.

Full WordPress plugin testing guide → · Mobile app & mobile web testing →

A real WordPress site, provisioned in seconds, destroyed after your test. Not a simulation — each tester gets their own wp-admin login, your plugin installed and activated, on a live subdomain.

Built for plugin and theme developers who need human QA before they ship — without spinning up staging, sharing credentials over Slack, or hoping testers know how to install a zip.

Toggle "WordPress plugin test" when you create a test, upload your .zip, and QATested handles the rest. Each claimed slot gets an isolated sandbox — testers never share an environment.

WordPress login — per tester

Open WordPress

your-plugin-a1b2c3d4.sandbox.qatested.io

wp_admin_847291
••••••••••••
Log in to wp-admin, test the installed plugin on the front end and in settings, then record and submit structured feedback.
1

Upload plugin zip

2

Sandbox provisions on claim

3

Tester gets WP credentials

4

Tests, records, submits

5

Sandbox destroyed at settlement

WordPress version

Latest stable WordPress on a clean install — no theme clutter, no mystery plugins. Your uploaded plugin is installed and activated automatically.

What else is installed?

Nothing by default. It's a fresh WordPress stack so you see exactly how your plugin behaves on a typical site. Pre-installed stacks (WooCommerce, Yoast, etc.) are on the roadmap.

Pricing

+$4 per slot on top of your normal tester pay and platform fee — covers provisioning and hosting each isolated sandbox.

Instance lifetime

Each sandbox is created when a tester claims a slot and destroyed automatically when your test settles — typically within a few days of your deadline.

Reserved instances have a 30-day maximum life on the hosting side. For most tests, sandboxes are gone long before that.

Post a WordPress test

WordPress sandbox testing is in beta and open to every developer account. Toggle WordPress plugin test when you create a test — upload your zip and go. No waitlist.

Exports

Your QA data, ready to share.

Submission review happens in the app — but your team probably lives in spreadsheets, docs, and issue trackers. Export files without wiring up an API, or send a finding to Jira, Linear, GitHub, or Slack in one click.

Copy a wide table for Google Sheets or Excel, download CSV or JSON, or grab a ZIP with screenshots and MP4 recordings. Filter by status before you export if you only want approved submissions. Tracker handoffs are one-way create/post — not two-way sync.

Export — Checkout flow test
Copy table for spreadsheet TSV
CSV — submissions (wide) .csv
ZIP archive CSV + JSON + images + MP4
Markdown report .md
Payment & refunds

Pay for results, not effort.

You only pay for submissions you approve. The mechanics are automatic — no manual transfers, no chasing refunds.

Pay upfront to reserve slots

When you publish a test, the total slot value is charged to your card. This funds are held and released to testers as you approve submissions — not before.

Approve to release payment

When you approve a submission, payment is released automatically to that tester's Stripe account. You can approve as submissions arrive — you don't have to wait until the deadline.

Unused slots refund automatically

If a slot goes unfilled, or if you reject a submission and no one else claims the slot before the deadline, that slot's value is automatically refunded to your original payment method.

Pricing

Pick a package. Post a test.

Pay only for approved work. Customize slots anytime.

Friction map + ship call — before customers hit the warts.

Total $84.00

5 testers · $14 each · platform fee included

Customize slots & pay
5
Min 3 · Max 20
Product session · ~30–45 min
Post your first test Free to join — pay only when you post a test.

Also sample live visitors? See Usage pricing →

New · After you ship

Keep learning from real visitors with Usage Learnings.

Tester slots cover you before and as you ship. Afterwards, one snippet samples real visitor sessions on your live product — DOM replay, friction points, and AI-drafted findings. Any finding can become a QA test in one click. 25 sessions free when you enable it.

Explore Usage Learnings →
Optional walkthrough

Prefer a picture? About 90 seconds through a full test cycle — post, record, answers, approve.

FAQ

Common questions from developers

Structured QA vs crowdtesting, automation, and research tools — plus pricing, fill rates, rejections, and exports.

Is it free to create a developer account?
Yes. Signing up is free — explore the dashboard, browse templates, and poke around with no charge. You only pay when you post a test (tester pay plus the platform fee at checkout).
What's the minimum to post a test?
Three testers at $5 each, plus a 20% platform fee — about $18 at checkout. You can raise slot count and pay per tester from there; the pricing calculator shows your total before you publish.
What is the platform fee?
20% on what you pay testers. On an $8 slot, that's $1.60 to us if it's approved. Covers ID verification, Stripe, and running the platform. Nothing extra shows up at checkout.
How is this different from Testlio or uTest?
Testlio and uTest are built for enterprise teams — sales calls, custom contracts, and often pay-per-bug models. QATested is self-serve: post a test, checkout via Stripe, and pay per approved slot with no sales call. You own the feedback form, get in-browser recordings, and can export everything without an account manager.
How is QATested different from cheap crowdtesting platforms?
Crowdtesting platforms sell low-cost usability sessions: someone records their screen and tells you what felt confusing. That is useful early, and it is not what we do.

QATested is structured QA. You define the report form, the devices and browsers, and the pass criteria. Testers are verified and tiered, submissions come back as reviewable evidence with screenshots and recordings, and you approve or reject each one — you only settle for work you accepted. Unused slots refund.

We also cover environments most session tools skip: clean WordPress plugin sandboxes with credentials, staging logins, and Usage capture on your live product that turns real user friction into a funded retest.
Why not just use Cypress or Playwright?
Keep them. Automation catches regressions you already scripted — excellent in CI. QATested is the human layer after builds go green: real people on real devices follow your brief, record the session, and file structured findings you approve or reject. Scripts miss confusing copy, awkward flows, and bugs you never wrote an assertion for.

Many developers run both — automate what you know, then post a short human smoke or bug hunt on staging before you ship. After CI is green, the Customer Deploy API can open a draft test from your pipeline.
How is this different from Maze or UserTesting?
Keep those for prototypes and research studies — design validation, unmoderated tasks, panels, and usability metrics. Maze tells you if the design works. QATested tells you if the build is ready to ship: your staging URL or WordPress sandbox, your custom report form, screen recordings, and approve/reject on every submission. You settle only for work you accepted.

Many teams use research tools earlier, then post a short human QA run on the real build before release.
How quickly will I get submissions?
Honest answer: we're early, so the tester pool is still small. Pay matters — a $20 slot usually fills faster than $5. Looser device requirements help too.
What if not all my slots fill?
Unfilled slots are automatically refunded to your original payment method when the test deadline closes. You only ever pay for completed, approved submissions.
What if a tester submits poor work?
You review every submission individually before approving it. Incomplete or off-brief work can be rejected — the slot reopens, and you pay nothing for that submission. Thorough work with hard feedback should be approved; that’s what independent testing is for. We moderate rejects so both sides stay treated fairly. Full trust overview: Why developers trust QATested →
Can I require a minimum tester tier?
Yes. When setting pay per slot, you can gate tests to Rising, Top, or Elite testers — tier is based on rating, approval rate, and completed tests. Higher pay tends to attract higher-tier testers faster.
Can I test WordPress plugins?
Yes — toggle WordPress plugin test when you create a test and upload your plugin zip. Each claimed slot gets an isolated WordPress sandbox with wp-admin credentials. Sandboxes add $4 per slot. See the WordPress testing page for full pricing, privacy, and sandbox details.
Can I create tests from CI or my own app?
Yes. After CI is green, the Customer Deploy API lets you create a draft with an API key, then pay via Stripe Hosted Checkout or the in-app checkout link. Keys live under Dev → API after you sign in.
Can I test a mobile app?
Yes. When creating a test you specify target devices and browsers. Testers must match your requirements to claim a slot. Screen recording works in-browser on desktop and mobile, with an external link as a fallback. See the mobile testing page for iOS, Android, and mobile web workflows.
Do testers record their screen?
Yes — every submission includes a screen recording. Testers capture sessions in-browser inside QATested (no Loom account or extra tool required). An external link works as a fallback. You watch playback in your dashboard and can export MP4 files with your submission data.
Can I test software behind a login?
Yes. Attach staging username, password, and login steps when you create a test. Claimed testers get one-tap copy-and-open access — no sharing credentials over email or Slack.
Can I export submission data?
Yes. Copy a spreadsheet-ready table, or download CSV, JSON, Markdown, or a ZIP with screenshots and MP4 recordings — including wide-format CSV for spreadsheets. From review, you can also send a finding to Jira, Linear, GitHub Issues, or Slack — one-way create/post into tools you already use, not two-way sync. Export from your test dashboard after sign-in; no API keys required for file export.
What about after I launch — can I see how real visitors use it?
Yes — that's Usage Learnings, a separate product. One snippet samples real visitor sessions on your live product: DOM replay, friction points, and AI-drafted findings. You get 25 free sessions when you enable it, and any finding can be turned into a QA test in one click.
Ready?

Post your first test today.

Free to join — pay only when you post a test. Five minutes to set up. No sales call, no minimum spend.

Post your first test Read the FAQ

Looking to earn by testing software instead?

See how testers work →