Pre-release checks
- Confirm every translated file still parses as valid JSON.
- Verify placeholders, variable tokens, and formatting markers survived intact.
- Spot-check protected words such as brand names, SKU labels, and technical terms.
- Review empty states, error states, checkout, and authentication screens in the target locale.
- Check for truncation on mobile widths, not just desktop.
Post-merge checks
- Run one smoke test in the live build artifact, not only in local development.
- Keep a short list of strings that were manually corrected so future batches reuse better wording.
- Capture recurring translation issues and add them to the protected-word or review workflow.
Originally published on the JSON Translate blog.
Top comments (0)