What is What to Test in TestFlight?

What to Test belongs to a build, not to a group. When you add a build to a group in App Store Connect, Apple asks what you want testers to focus on, with optional versions in other languages, and the note is shown to testers in every group that has the build. Testers see it in the TestFlight app.

It is the build’s half of the test information. The app’s half (the beta app description, feedback email and Beta App Review contact) is set once per app and reused for every build. What to Test changes with each build, so it is the part you write every time: what is new, what to try and what to ignore.

For internal groups the note is optional. For external groups a build needs one before it can go to Beta App Review.

In VibeView. The Submit dialog has a What to Test field of up to 4,000 characters, written in the app’s primary language. It is required while an external group is chosen, and Reuse last notes copies in the previous build’s notes; it never fills itself. What to Test, by language adds other languages. From the command line, pass --what-to-test or --what-to-test-file to vibeview submit, and --notes-dir with one <code>.txt file per language (CLI 0.58.0 or later). Notes are never read from vibeview.json, so an old note is never sent by accident. See What to Test notes.