How TestCrew Return Testing Works

TestCrew’s return-testing feature helps you organize the relationship between people who joined your recruitment and the apps you may test in return.

Managing mutual testing only through direct messages or personal notes makes it easy to forget who has already been helped. The return-testing view lets you track participation, verification, feedback, and completion more systematically.

The basic return-testing flow

1. A participant joins your app’s closed test
2. You review the participant’s profile and available app listings
3. You choose a listing you can realistically test
4. You join the other developer’s closed test
5. You install the app and complete the requested actions
6. You submit feedback or a completion report
7. You update the return-testing status in TestCrew

The exact screens, rewards, and completion rules may change. Follow the current instructions shown in the app.

What to check before accepting a return test

Device compatibility

Confirm that the other app supports your Android device and Android version.

Google account

Use an account that can join the tester group or other eligibility method configured by the developer.

Recruitment deadline

Do not join a listing that has expired, has been paused, or has already reached its required participant count.

Requested test scope

Confirm that you can perform the requested actions. Some apps may require sign-in, photos, location access, notifications, payments, or special hardware.

Required participation period

For a Google Play closed test, do not leave the program early. Maintain participation for the period specified by the developer and by the applicable Google Play requirement.

Return testing is more than opening a link

Before marking a return test complete, perform at least the following:

• Join the test with the correct account
• Install the app from Google Play
• Launch the app
• Use the requested features
• Report whether the tested flow worked

Even when you find no issue, state what you actually checked.

Tested on a Galaxy S23 running Android 15.
Registration, sign-in, data saving, and restoration after restarting all worked in the requested scope.
I did not find a major problem in those flows.

When you cannot provide a return test

You may not be able to test every participant’s app under the same conditions.

Examples include:

• You only have an iOS device
• Your Android version is unsupported
• You cannot meet a required country or language condition
• The app is incompatible with your device
• The test requires a real payment or specialized equipment
• You are already maintaining too many simultaneous tests

Do not mark the work complete when you could not perform it. When possible, tell the other developer why you cannot participate.

Tracking return-testing status

A simple status table can prevent missed or duplicate work.

Also confirm that you have not accidentally tested multiple apps for the same obligation or counted the same action twice.

Rules that reduce disputes

Read the conditions first

A listing described as available for return testing may still have limits involving participant count, deadline, device, country, or operating system.

Do not leave immediately after joining

Leaving can affect the other developer’s closed-testing state and production-access preparation. Remain opted in until the requested period or confirmed completion.

Avoid generic reports

Do not submit the same short message for every app. Name the features and flows you actually tested.

Protect personal information

Before sharing screenshots, hide Google account details, email addresses, notifications, authentication codes, and payment information.

Do not post defects as public reviews

During closed testing, send issues through the feedback channel specified by the developer. The goal is to help improve the app before public release.

How return testing relates to credits

Testing another app may also contribute to TestCrew credits and the wider recruitment cycle.

However, track return-testing obligations and credit balance separately.

• People you may need to help: return-testing list
• Recruitment capacity available to you: credit balance
• Reward and spending rules: current in-app terms

See How the TestCrew Credit System Works for the credit flow.

Responsibilities of the developer who recruited testers

After someone joins your app, confirm the following:

1. Could the participant opt in?
2. Could they install the app?
3. Did they test the requested core features?
4. Did you respond to questions or defect reports?
5. Did you tell them when a fixed version became available?
6. Do they have an active listing that you can test in return?

Ignoring participant questions can cause confusion and early withdrawal from the test.

Summary

Use return testing to reduce missed obligations in mutual testing.

• Read the other listing’s conditions
• Join with the correct Google account
• Install and actually use the app
• Share specific results
• Maintain participation for the required period
• Track the status in TestCrew

For the broader principles, see What Is Mutual Testing for Google Play Closed Tests?.