String Catalog Logo
String Catalog
Home
Docs
TestFlight WhatToTest Parser Reference

// Parsers

TestFlight WhatToTest Parser Reference

Localize TestFlight What to Test notes across iOS languages. Covers WhatToTest.txt detection, BCP-47 locale matching, and review state propagation.

TestFlight parser support is dedicated to iOS WhatToTest.<locale>.txt files.

When To Use This Parser

Use this parser when your iOS app release process includes localized TestFlight "What to Test" notes and you want those notes managed in the same localization workflow as the rest of your content.

Detection Rules

  • Path should follow TestFlight/WhatToTest.<locale>.txt
  • Locale codes are validated against supported BCP-47-style formats

Supported File Patterns

  • TestFlight/WhatToTest.<locale>.txt for base and non-base locales.

Parsing Behavior

  • Reads plain-text What-to-Test content per locale file.
  • Associates each locale variant with one canonical file identity for stable tracking.

This canonical mapping is important for consistent state tracking when multiple locale files represent one logical TestFlight note set.

Locale Normalization Behavior

  • Uses BCP-47 validation and normalization for locale matching.
  • Keeps per-locale output while tracking through canonical base identity.

Example:

  • TestFlight/WhatToTest.es-419.txt
  • TestFlight/WhatToTest.fr-FR.txt

map to canonical identity such as:

  • TestFlight/WhatToTest.en-US.txt

Review State Handling

If base-language content changes, existing non-base localizations are marked NeedsReview.

Rename Handling

TestFlight file handling is path- and locale-driven; rename-aware key matching is not a primary behavior in this parser.

Write-Back Normalization

Writer generates one file per language using normalized BCP-47 codes.

Expected Outcome

After sync, each active locale gets its own normalized What-to-Test file while the system keeps one canonical identity for parser state and review propagation.

Edge Cases Handled

  • Multiple locale variants that must resolve to one canonical file record.
  • Base-language updates that should fan out to non-base review state.
  • Locale files arriving out of order across sync runs.

Common Mistakes

  • Using an unsupported file naming pattern and expecting parser detection.
  • Editing only non-base locale files and expecting global review propagation.
  • Treating TestFlight files as generic text files instead of parser-scoped localization assets.