Short answer: TestFlight groups let you send different builds to different sets of testers. Apple describes groups as how you organise and distribute builds, and you can create several and add different builds to each. A common setup has one internal group plus external groups for the public beta, new features and regression checks.
Why groups matter
Without groups, every tester gets every build, which tires out your best testers and mixes up feedback. Groups let you match builds to goals, and Apple's tester metrics let you see who is engaging.
A setup that scales
Internal: Team
Everyone on the team with a qualifying role, with automatic distribution on. Every build goes here first.
External: Core beta
Your most reliable outside testers. They get stable builds and are asked for detailed feedback.
External: Public beta
A public link group for wider feedback. Set device and OS criteria if needed.
External: Feature preview
A small group for an experimental feature, so most testers aren't affected.
External: Regression
Testers who rerun the same checklist on each release candidate.
Writing different notes per build
The "What to test" notes should match the group's job. Feature preview: "Try the new export screen and tell us what's confusing." Regression: "Run checklist A and report any step that fails."
Using tester metrics
Apple says you can view tester metrics to evaluate engagement and manage participation. Move consistently engaged testers into the core group, and check in with quiet testers or replace them, especially in small groups where one silent tester is a big share.
Housekeeping
Remove testers who have finished, disable public links when groups are full, and keep a record of which build each group tested. Apple allows up to 100 builds, so clear naming helps.
Adding outside testers to a group
If a testing service runs a round for you, give them their own external group so their feedback is easy to separate. TestLancer testers join through your TestFlight invite or public link.
The official TestFlight facts
From Apple's TestFlight overview:
- You can add up to 100 internal testers from your team (Account Holder, Admin, App Manager, Developer or Marketing roles).
- You can invite up to 10,000 external testers by email or public link.
- External testing needs a beta app description and beta app review information, and your first build in an external group must be approved by App Review for TestFlight.
- You can share up to 100 builds, and testers can use your betas on up to 30 devices.
- Public links can have criteria such as device type and OS version, and you can see how many people viewed and installed from the link.
- Testers send screenshot feedback and crash reports, which you read in the TestFlight section of App Store Connect.
Quick checklist before you invite external testers
- [ ] Beta app description written in plain language: what's new and what to try.
- [ ] Beta app review information filled in, including a demo account if the app needs sign-in.
- [ ] A feedback email you actually check.
- [ ] Separate groups for different goals (for example, a new-feature group and a regression group).
- [ ] Public link criteria set if you only want certain devices or OS versions.
- [ ] A tester brief with three or four concrete tasks.
- [ ] A plan to read screenshot feedback and crash reports at least every other day.
- [ ] A note of what you'll change before submitting the final build for App Store review.
Mistakes that slow down a TestFlight beta
- Sending the first external build without review notes. Reviewers need to know how to reach each feature.
- A demo account that expires. Check it works the day you submit.
- One giant group. Separate groups keep feedback focused and avoid sending risky builds to everyone.
- Leaving a full public link open. Apple suggests disabling it once you reach your limit.
- No "What to test" notes. Testers who don't know what changed rarely find what you care about.
- Ignoring crash reports until launch week. Read them every few days while testers still remember what happened.
- Asking testers for App Store reviews. Keep beta feedback private and honest; TestLancer never sells reviews or ratings.
FAQ
Can a tester be in more than one group?
Testers can access builds you've shared with them. Keep groups clear so feedback stays easy to read.
Does each external group need beta review?
Apple says builds are sent for review once added to a group. Check each build's status in App Store Connect.
How big should a group be?
As small as its goal allows. A feature preview might need ten people; a public beta may need hundreds.
Next step
If you need real people to test your iOS build on their own iPhones and iPads, TestLancer's iOS app testing recruits testers for TestFlight builds and returns bug reports with steps to reproduce. TestLancer does not sell reviews, ratings or installs, and nobody can promise that App Review will approve a build. You can start a project at testlancer.com.
Top comments (0)