Test swap: find testers for Google Play by testing other developers’ apps

What a test swap is

It is a group of developers in the same situation as you: everyone brings an app and opts in as a tester to everyone else’s apps. Nobody pays: in exchange for testers you spend a little time on the others’ apps.

It works because everyone has the same interest: staying opted in for the whole test and really using the apps, otherwise nobody gets to publish.

How many members you need

In a swap group each app is tested by all the other members: in a group of 5 people, your app has 4 testers.

To reach Google Play’s 12 testers with a single group you therefore need 13 members, you included. Alternatively you can add up testers from several groups (for Google each person counts only once) or pair the swap with an “I need testers” group, where testers only try your app.

It’s worth staying a little above the minimum: if someone leaves before 14 days, they no longer count for Google.

How to create a group

You need a TestersSeeker account and your app with its closed test links: the one to opt in as a tester and the one to download it. Then:

1. From “Test swap” press “Create group” and choose the app you bring.
2. Name the group and choose the number of members and how many days the test lasts. If the goal is Google Play closed testing, choose at least 14 days.
3. Set the rules: automatic entry or with approval, and after how many hours (24, 48 or 72) you can free the spot of anyone who doesn’t complete the procedure.
4. The group appears in Explore and on the Home page and fills up as other developers join.

How to join a group

In Explore you find the open groups, with free spots, duration and members. Press “Join” and choose which of your apps to bring; if the group requires approval, the request goes to its creator.

You need your Google Play email: it is the one the others add to their app’s tester list.

You can also join as a plain tester, without a swap: you test the apps of all the other members, but nobody tests an app of yours.

Until the group is full you can withdraw with “Leave the group”, with no penalty.

When the group is full

The group moves to “My tests”, with the mailing list, the app links and the group chat. The steps, in order:

1. Copy the mailing list into your app’s tester list in the Play Console and press “I added the emails”.
2. For each of the others’ apps press “Become a tester” to opt in to the closed test, then “Download the app”. The links become active once that person has added you to their tester list.
3. When you finish the procedure for an app, press “I did it” on its row: you confirm that you opted in and downloaded it.
4. The “Who did your app” box shows who opted in to yours and who is still pending.
5. When everyone has completed the procedure for every app, the test countdown starts.

During the test

Really use the others’ apps and stay opted in until the countdown ends: for Google anyone who leaves before 14 days doesn’t count, and if they come back their days start over.

In the group chat you can report problems, ask what to try and collect feedback on your app: you will need it to answer Google’s questions for production access.

If someone doesn’t complete the procedure within the chosen time, the creator can free their spot: the group opens again and, when someone new joins, everyone adds their email to the tester list and confirms again.

At the end of the test

When the countdown ends everyone leaves feedback on the apps they tested, with a rating and a comment, and rates the developers. The completed test counts towards the profile’s reputation and level.

At that point, if your app has had at least 12 testers for 14 days in a row, you can apply to Google for production access.

Tips for a swap that works

Do your part right away: as long as even one procedure is missing, the countdown doesn’t start for anyone.

Look at the profile of whoever joins: level, completed tests and feedback received. If you want to choose yourself, create the group with entry by approval.

Anyone who misbehaves can be reported to the moderators and blocked.

Update your app during the test and reply to whoever reports problems: it is exactly what Google wants to see.