NK
← All work
05 —SaaSMobile appWeb platformLive · 2026
TestBunny logo

12 testers, 14 days. Every day on record.

Real testers for Google Play’s closed-testing requirement: a per-campaign plan, real tasks every day, day-by-day participation and a report built on records, in one panel.

Visit the site — www.testbunny.co
TestBunny — 12 testers, 14 days. Every day on record.
Colophon
Category
SaaS · Android testing platform
Platform
Web panel · Android app
Interface
Turkish · English
Model
One-time payment per app; no subscription
By the numbers
12
testers, Google’s minimum
14
days of continuous opt-in
8
phases in the task plan
10
task types

Google Play requires new developer accounts to run a closed test with at least 12 people for 14 continuous days before going to production. Most developers treat it as a number to hit, but Google checks whether testing really happened. Without an answer to who tested what, and when, the production-access application is weak.

TestBunny fills that gap with records. Testers join campaigns that match their device, Android version, country and language; they complete the Google Group and opt-in steps within 72 hours; and they do a written task every day in an 8-phase plan from install to regression. The app owner accepts each submission or rejects it with a reason, and confirms bugs. Once 12 people × 14 days are done, the production-access prep report is built straight from the records.

Testers are never paid in cash: they earn credits for accepted tasks, confirmed bugs and participation, and spend them on testing their own apps. The web panel, the Android app and the server run on the same open rules, and nothing unverified is shown as verified.

08
01

Matching tests, with reasons

Transparent scoring by device, version, country and language; each tester joins at most 3 campaigns at once.

02

Group, opt-in, install

Google Group and opt-in within 72 hours; self-reported steps are clearly labelled.

03

A real task every day

8 phases from install to regression and 10 task types; expected vs actual in writing, evidence optional.

04

Everything on record for the owner

Accept, reject with a reason, confirm bugs and rate both ways; clean submissions not reviewed in 72 hours are accepted automatically.

05

Day-by-day participation

Daily active testers shown against Google’s threshold; 2 inactive days puts a tester at risk, 4 drops them.

06

Production-access prep report

A summary for Google’s questions where every sentence links back to a record.

07

Free replacement

Testers who leave in the first 7 days of a campaign are replaced.

08

Credits, not cash

Credits for tasks, bugs and participation, spent on testing your own app and never cashed out.

01 / 06 — Swipe →
Landing page
01
Landing page

12 testers, 14 days; the panel and the Android app at a glance.

My apps
02
My apps

All apps, credits and live campaigns on one screen.

Campaign
03
Campaign

Day rings, daily activity, platform data and the next step.

Testers
04
Testers

Each tester’s device, day strip and tasks.

Report
05
Report

A records-based summary for the production-access questions.

Android app
06
Android app

Testers handle tasks, credits and their profile in the Android app.

Next project — 01
Rocketly CRM

An AI-native CRM that puts a company’s entire customer operation on one screen

(—) Contact

E-mailnoyan@noyankalay.com
Local time in Istanbul
--:--
Instagram
@noyan.kalay

I usually reply within 24 hours.