For developers
Google Play requires personal developer accounts created after November 13, 2023 to run a closed test with at least 12 testers opted in for 14 consecutive days before applying for production access. Here's how TestersWiz gets you through it — verifiably.
- 1
Install another developer's app
This comes first, and it is the price of listing — you never need a payment or a card for it. Join another developer's test on the marketplace, install the app, and upload a screenshot of it running. That earns 1 Wizbit the moment it uploads, and listing your own app spends it. You do not have to finish the 14 days first. On an empty marketplace listing is free, because there is nothing to test yet.
- 2
List your app with the Wizbit from step 1
Enter your app name, package id, and your closed-testing opt-in link from Play Console (Testing → Closed testing → Copy link). It spends the Wizbit from step 1 and needs no card — your app goes live on the marketplace immediately. Cancel any time before the 14-day clock starts.
- 3
Trade tests to fill your 12 seats
Find another developer's app and propose a trade: you test theirs, they test yours. It lands in their mailbox; when they accept, both of you are enrolled at once. You can also accept developers who volunteer to test your app solo. Every trader shows a public record — trades completed, trades failed, recent strikes — so you know who's reliable before you shake hands.
- 4
Verify opt-ins against Play Console
Open Play Console → your closed-testing track → Testers, and check each submitted email off in TestersWiz as you see it appear. This is the anti-fraud heart of the product: nobody is 'in' until you've seen them in Google's own list. In a trade, each side verifies the other — evidence only you can see.
- 5
The 14-day clock runs
The clock starts the moment you admit your first verified tester — no need to wait for all 12. Each new tester you admit restarts it, so the whole group tests the full window together. Nothing caps how many you take: 12 is Google's requirement, and every tester past it is cover for one who drops out. Our daily job advances the day counter; testers submit a screenshot check-in on day 3. Ship an update inside the window if you can — Google looks for iteration, not a frozen build.
- 6
Confirm and rate
After day 14 the campaign asks for your confirmation. Review the evidence, dispute any tester who didn't hold up their end (a human admin reviews — no auto-bans), confirm the rest. Confirming completes any trade the seat came from and builds each tester's public reputation. Whoever bails on a trade — drops out, ghosts a verification, cancels mid-trade — takes a strike; 3 in 30 days pauses their trading.
Ready when you are
Listing needs no money. It costs 1 Wizbit, which you earn when you install an app you are testing and upload a screenshot of it running. You do not have to finish the 14-day test first: the Wizbit arrives the moment your screenshot uploads. Seats also fill fastest for developers who are testing someone else's app, so step 1 is working for you twice.