Closed testing tester swaps: where to find them and where they fall apart

1. What a tester swap is

A closed testing swap is when developers in the same situation join each other's apps as testers. You become a tester for their app, and they become a tester for yours. It costs nothing, and it's usually the first thing people look for when they don't know 12 people with Android phones.

You can get the headcount quickly. The hard part comes after. The requirement is only met when 12 testers stay opted in continuously for 14 days, and once a swap partner's own test is done, they have no reason to stick around.

2. Where to find swap partners

• Chat groups. Search Discord or Telegram for ‘closed testing’ or ‘tester swap’ and you'll find several groups where developers test for each other. They respond the fastest.
• Developer communities and forums. Post that you're looking for testers on places like Reddit or Facebook groups, and exchange emails in the comments.
• Communities in other countries. There are tester-swap boards in other languages too. But your partners can only install your app if their country is included in your track's countries/regions.

In your post, include your app name, the opt-in link, how long people need to stay, and the date your test ends. The clearer it is what they need to do and until when, the more people stay to the end.

3. How it works, step by step

1. Upload a release to your app's closed testing track and confirm that the review is done and the opt-in link is visible.
2. Collect the Google account emails of the people you're swapping with, add them to your tester list, and send them your email too.
3. After saving the list, send the changes for review from Publishing overview. If you skip this step, your partners can't join.
4. Each of you accepts the invitation through the other's opt-in link and installs the app.
5. The 14 days count from when the 12th person joins. During that time, nobody uninstalls, and everyone opens the apps about once a day.
6. Once you meet the requirement, apply for production access — and keep your partners' apps installed until their tests are over.

4. Four ways it falls apart

• Your partner finishes first and uninstalls. This is the most common. A partner who started a week before you is done when you're about halfway through your 14 days. If they uninstall then, they drop out of your count.
• They opt in but never use the app. They count toward the headcount, but when your production access application is reviewed, Google also looks at whether testers actually used the app. A test nobody opened can be sent back for “insufficient engagement.”
• Everyone joins on different days. The 14 days count from when the 12th person joins. If people trickle in one at a time over several days, your end date gets pushed back, and if you fill an empty spot, the 14 days start over from that person.
• The apps you have to keep pile up. Swap with 12 people and you have 12 other apps on your phone, each of which you can't uninstall until that person's test is over. If you uninstall, you break their requirement.

5. How to keep it going to the end

• Keep extra testers. With exactly 12, one dropout breaks it. Get a few more.
• Start all at once. Gather everyone first and have them join on the same day. That keeps the period as short as possible, and everyone's end dates line up.
• Exchange end dates. Write something like “My test ends on ○○/○○. Please keep the app installed until then,” and note down your partners' dates too.
• Check the headcount along the way. Every few days, look at the number of opted-in testers in the requirement progress on your app dashboard. If it drops, refill right away to minimize the delay.
• Actually use the apps and share feedback. If you open each other's apps and send a line about anything that bugs you, you'll have something to write under “feedback received” in the application questionnaire.

For how to check that your headcount and duration are actually holding, see When do the 14 days start?.

6. What Google says

The Play Console Help Center suggests recruiting testers from your personal network (friends, family, coworkers), online groups of people likely to use your app, and social media. It doesn't address tester swaps specifically.

There are two things the documentation states clearly: let testers know they need to stay opted in for 14 days, and if you have fewer than 12 testers or engagement is too low, you'll need to test more. Even with a swap, you have to meet both.

In the application questionnaire, describe truthfully how you recruited testers and what feedback you received. For what to write for each question, see production access questionnaire examples; for reasons applications get sent back, see 7 reasons for rejection.

7. When a swap isn't the right fit

If you have a fixed launch date, or you don't have time to look after 12 other people's apps for 14 days, a swap isn't a good fit. If it breaks once, the whole 14 days start over. You can compare four approaches, including recruiting people you know and using a service, in How to find 12 testers.

DUIRE is the service option. We install your app on real Android devices signed in with tester accounts, run it at set times every day for 14 days, and keep per-device run records. No other people's apps on your phone, and no checking who uninstalled what.