Before you order

Is your app ready to be tested?

Ten questions, two minutes, no sign-up. By the end you will know whether we can start tomorrow, or what is left to prepare in your Play Console. Nothing is sent until you click: everything happens in your browser.

Start the checkSee pricing

Why we put you through this

We charge for the test before running it, and we run it again free of charge if Google rejects it for insufficient testing. That guarantee only holds if we refuse to start tests that are doomed from the outset. An app that is not yet on a closed track, or that is not distributed in our testers' country, cannot be tested — whatever you pay. Better to find out now.

The ten points Google looks at

Answer in order. Points marked blocking physically prevent the test from starting; the others degrade its quality or delay the launch.

0 / 10 — Answered

  1. 1Is your developer account a personal account created after 13 November 2023?

    That is the only case where 12 testers for 14 days is mandatory. Play Console → Settings → Account details.

  2. 2Is your app already published on a closed testing track? blocking

    Closed track only. Internal and open testing do not count towards the 14-day requirement.

  3. 3Which API level does your latest bundle target? blocking

    Since 31 August 2026, uploads must target API 36 (Android 16). Shown in Play Console → App bundle explorer.

  4. 4Your closed track's opt-in link blocking

    Play Console → Testing → Closed testing → Testers tab → “Copy link”. It looks like https://play.google.com/apps/testing/your.package. If you prefer to supply an address list, write “e-mail list”.

  5. 5Your app's package name

    For example com.example.myapp. It appears at the top of your app's page in Play Console.

  6. 6Is your app distributed in our testers' countries? blocking

    Play Console → Distribution → Countries and regions. Our testers are mainly in Algeria, France and French-speaking North Africa. A tester cannot install an app that is unavailable in their country.

  7. 7Your privacy policy address blocking

    A public page, reachable without logging in. It is mandatory for every published app, and its absence is a frequent rejection reason — unrelated to testing.

  8. 8Is the “Data safety” form completed and approved?

    Play Console → Policy and programmes → App content. Not our scope, but its absence blocks production access even after a flawless test.

  9. 9Does your app require an account to be used?

    If so, testers need demo credentials, otherwise they are stuck at the login screen.

  10. 10Does the flow to be tested require a real payment?

    Subscription, non-testable in-app purchase, or a paid app.

Answer the ten points

The verdict will appear here, together with the summary to send us.

The 1 November 2026 trap

Since 31 August 2026, every new app and every update must target Android 16 (API 36) to be published. Developers who requested an extension in Play Console have until 1 November 2026 — a few weeks away. After that date, an upload targeting API 35 is rejected, closed testing included: your test would stop dead. If this is your case, raise the API level before ordering, not during.

Questions that come up before ordering

Do internal or open testing count?
No. Google only counts testers on a closed testing track. Internal testing (up to 100 people, no opt-in) and open testing do not satisfy the 12-testers-for-14-days requirement. If your app sits on another track, create a closed track and publish your bundle there — it is free and takes ten minutes.
My app is not distributed in Algeria or France. Does that matter?
Yes, it is a blocker. A tester can only join your track if your app is available in their country. Availability is set in Play Console → Distribution → Countries and regions, it is independent of your app's language, and it changes nothing for your real users. Tell us where your target users are: we build the cohort accordingly whenever we can.
Do I have to give you access to my Play Console?
Never, and we would refuse it. All we need is your closed track's opt-in link, or you add our list of e-mail addresses. We ask for no Google credentials, no developer access, no source code.
My app requires a login. How do your testers get in?
Give us a demo account, or a multi-use invitation code. Without one, testers are stuck at the login screen from day one: they will log their attendance but never exercise the main flow — and real usage is precisely what Google has been looking at since 2026.
What if I cannot answer a question?
Answer “I don't know”. It is not disqualifying: the summary will flag it, and we will check together before any invoice. We would rather have a stated uncertainty than a box ticked at random.
My developer account is an organisation account.
Then the 12-testers-for-14-days requirement does not apply to you: it only targets personal accounts created after 13 November 2023. We would rather tell you plainly than sell you a test you do not need. User testing is still useful for finding bugs — but it is no longer an obligation, and you should be able to decide knowing that.

Unsure about an answer?

Write to us with your summary: we will tell you in a single reply whether the test can start, and how soon.

Write to us Back to pricing