How a 99tests run works, from payment to report in 3 business days
What happens after you pay for a 99tests run: what to send, how testers are matched to your devices, what a session is, how findings are verified, and what's not included.
In this article
- The short version
- Step 1: Pick a package
- Step 2: Send your cases and your build
- Step 3: See the plan before it runs
- Step 4: Testers who own your devices take the sessions
- Step 5: Timed sessions on real devices
- Step 6: Verification, then the report
- What's not included
- Ordering from your coding agent
- Start a run
Most testing services start with a call. 99tests starts with a checkout page. This post answers the questions people usually save for that call: what you send, who sees your build, what happens hour by hour, and what you get at the end.
The short version
| When | What happens |
|---|---|
| Minute 0 | You choose a package and pay by card. The invoice is issued at checkout. |
| Minute 2 | You upload your test cases, add the build link and pick target devices. |
| Minute 5 | Your cases are split into timed sessions by device, and you see the plan before anything runs. |
| Hour 1 | Offers go to testers who own your target devices. The first to accept takes the session. |
| Day 1–2 | Testers run your cases in timed sessions on their own phones, laptops and browsers. |
| Day 3 | Findings are checked, merged and graded, then the report arrives as a page and a PDF. Deep takes 5 business days. |
There is no account to create, no contract and no sales call.
Step 1: Pick a package
There are three, each a fixed price per run:
| Package | Sessions | Devices | Cases | Report | Price |
|---|---|---|---|---|---|
| Starter | 5 × 45 min | 2 | up to ~25 | 3 business days | ₹9,999 + GST ($129) |
| Standard | 10 × 45 min | 4 | up to ~50 | 3 business days | ₹18,999 + GST ($249) |
| Deep | 20 × 90 min | 6 | up to ~120 | 5 business days | ₹34,999 + GST ($449) |
A device slot can be a phone, a laptop or a browser, mixed freely in one job. Most teams start with Standard. If you need more coverage, add sessions in blocks of five.
One run covers one platform. A web app can mix phone browsers and laptop browsers in one job; an Android app, an iOS app and a website are three runs.
Indian customers pay in rupees with a GST invoice (add your GSTIN at checkout). Everyone else pays in US dollars. Nothing further is billed: no overage, no expenses, no change requests.
Not sure which package fits? The test plan builder counts your cases, and the QA cost calculator prices them.
Step 2: Send your cases and your build
Test cases, in whatever form you have them. CSV, Excel, a Google Sheets export, Word, Markdown or plain text, or exports from Jira or TestRail. Cases written by Cursor, Claude Code, Copilot or ChatGPT are fine as they are. You can upload up to five files, or paste. If you have none, start from our free test case library.
A build link. An APK, Google Play internal testing, a TestFlight public link, or a web address.
Target devices. For phones, a brand and a minimum OS version, or exact models from the phones our testers own. For laptops, a browser and an OS.
Step 3: See the plan before it runs
Your cases are split into timed sessions by device, so you can see which cases will run where before any tester starts. If you sent more cases than the package covers, the extras are listed up front as not run. They aren't dropped quietly.
Step 4: Testers who own your devices take the sessions
Offers go out within the hour to testers who personally own the phones, laptops and browsers you picked. Testers use their own devices on their own SIM and home networks: Jio, Airtel and Vi, home broadband and fibre. That's the point. These are the conditions your users have, not a clean device in a data centre.
If no tester with a particular device can take a session, it's credited back to you automatically.
Step 5: Timed sessions on real devices
Each session is 45 minutes (90 on Deep). The tester runs the assigned cases in order, records every serious finding as it happens with a screen recording or screenshots, and explores around the cases when something looks off.
Testers are paid for the session whether or not they find bugs, with bonuses for verified bugs. That keeps them following your cases instead of hunting for anything they can report.
Step 6: Verification, then the report
Testing and verification are separate jobs. Before you see anything, every finding is:
- checked for complete steps and evidence
- compared with the other findings on the job, and duplicates merged
- graded against a published severity rubric, with a confidence score
The report then arrives as a hosted page and a PDF. It has a summary verdict, every case against every device, the verified findings with recordings, the verification record, the session log and the list of what wasn't run. Here's what each section looks like.
After you fix the bugs, one click re-runs the same cases on the same devices against the new build.
What's not included
So there are no surprises, a 99tests run is manual functional and exploratory testing of the cases you send. It doesn't include:
- test automation
- security or penetration testing
- performance or load testing
- certification or audits
- desktop native apps
- writing your test cases
If you need those, use a specialist alongside us. Most teams keep their automated regression and add a 99tests run before releases that touch payments, login, onboarding or a store build.
Ordering from your coding agent
If you build with Claude Code, Cursor or VS Code, your agent can create the job through the 99tests MCP server and hand you a checkout link. You pay in the browser, and the verified findings come back to the agent. The setup is in the MCP docs.
Start a run
Pick a package, upload your cases and build, and testers start within the hour. To see the output first, read the sample report.
