Localization QA Checklist
Create a repeatable QA checklist for translations, RTL, formatting, and fallback behavior across locales.
Prompt
Create a localization QA checklist for [feature/product].
Context:
- Platforms: [web / iOS / Android]
- Locales to test: [list]
- RTL locales: [list]
- Date/number/currency requirements: [notes]
Provide a checklist grouped by:
1. Translation Coverage & Key Integrity
- Missing keys / fallback behavior
- Mixed-language UI detection
- Hardcoded strings detection
- Placeholder/variable correctness
2. Visual & Layout Validation
- Truncation/overflow/wrapping
- Line breaks, spacing, alignment
- Font support (diacritics, non-Latin scripts)
- Component density and readability
3. RTL Validation (if applicable)
- Mirroring rules
- Icon directionality
- Navigation order and focus order
- Animations and gestures direction
4. Formatting & Data
- Dates/times/time zones
- Numbers/decimal separators
- Currency symbol placement and rounding
- Sorting/search behavior (accent-insensitive, locale-aware)
5. Inputs & Validation
- Names/addresses/phone formats
- Input masks (if any)
- Error messages and helper text localization
6. Functional Flows
- Critical flows end-to-end in each locale
- Email/push templates (if applicable)
- PDFs/exports (if applicable)
7. Reporting
- Bug template (steps, locale, screenshots)
- Severity rubric (P0/P1/P2)
Format as a checklist QA can run in 30–60 minutes per locale.How to use
- 1Replace [feature/product], [web / iOS / Android], [list], and [notes] with your specific details
- 2Add context before the prompt: Describe your product, platforms, and locales. Example: "Product: Mobile app. Platforms: iOS, Android. Locales: English, Spanish, French, Arabic. RTL locales: Arabic."
- 3If you have existing QA processes: Mention your current QA approach. Say "We currently test [X]. Add to this: [describe]"
- 4Paste the modified prompt into your preferred AI tool, like ChatGPT or Claude
- 5Review the QA checklist: Check all sections (translation coverage, visual validation, RTL, formatting, inputs, flows)
- 6Customize for your product: Ask "Add checks for [specific feature]" or "Focus on [specific flow]"
- 7Export to your QA tool: Copy the checklist to TestRail, Jira, Linear, or your QA documentation
- 8Share with QA team: Use the checklist as a standard template for localization QA testing
- 9Update as needed: Refine the checklist based on actual QA findings
Pro Tips
- • Specify platforms: Mention "Web only" or "iOS and Android" so checklist is platform-appropriate
- • Include RTL locales: Mention "RTL locales: Arabic, Hebrew" so RTL validation section is included
- • Request time estimates: Ask "Estimate time per locale" to help plan QA schedule
- • For complex products: Ask "Create a checklist for [specific feature]" for feature-specific QA
- • Save as template: Reuse the checklist structure for future localization QA
