qe-localization-testing
Validate internationalization and localization across your product with systematic testing of translation completeness, locale-specific date/time/currency formatting, right-to-left language layouts, and cultural appropriateness. Detect hardcoded strings, verify Unicode support, and ensure native speaker quality before launching into new markets or adding language support.
qe-localization-testing validates multi-language products by checking translations, locale formats, RTL layouts, and cultural appropriateness across regions.
AI-generated summary based on this skill's SKILL.md
Install
proffesor-for-testing/agentic-qe/qe-localization-testing · repository language: TypeScript
git clone https://github.com/proffesor-for-testing/agentic-qe
cp -r agentic-qe/.kiro/skills/qe-localization-testing ~/.claude/skills/qe-localization-testingFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I test translations in my app with qe-localization-testing?
qe-localization-testing helps you validate translation completeness and quality across all supported languages. The skill guides you through systematic testing of translated strings, ensuring no text is missed and all translations are contextually appropriate. You can verify that every user-facing string has been properly localized and that translation coverage is complete before deployment.
What does qe-localization-testing check for RTL language support?
qe-localization-testing validates right-to-left language layouts for Arabic and Hebrew by testing UI mirroring, text alignment, and component positioning. The skill ensures that RTL layouts display correctly, navigation flows properly in reverse direction, and all interactive elements function as expected in right-to-left contexts without breaking the user experience.
How can qe-localization-testing help verify internationalization before launching in new markets?
qe-localization-testing provides a comprehensive framework for market-launch readiness by validating locale-specific formatting for dates, times, and currencies. It checks that your product handles regional preferences correctly, detects any hardcoded strings that bypass localization, and confirms Unicode character support. This ensures your product is genuinely ready for new market deployment.
Does qe-localization-testing detect hardcoded strings in my codebase?
Yes, qe-localization-testing includes checks to identify hardcoded strings that should be externalized for translation. The skill helps ensure all user-facing text is properly separated from code, making your product maintainable and fully localizable. This prevents strings from being missed during translation workflows.
What internationalization testing best practices does qe-localization-testing cover?
qe-localization-testing covers systematic validation of translation completeness, locale-specific formatting, Unicode character support, and cultural appropriateness of content. The skill guides you through multi-language testing strategies, helps validate translation file integrity, and ensures cross-locale format compatibility so your product works reliably across all supported regions.
Can qe-localization-testing validate Unicode and cultural appropriateness?
qe-localization-testing validates Unicode character encoding to ensure proper display across all languages and scripts. The skill also helps assess cultural appropriateness of content, checking for potentially offensive imagery, symbols, or phrasing that may not translate well or could alienate users in specific markets, supporting truly global product quality.
SKILL.md
rendered from the published skill — quoted content, verbatim
Localization & Internationalization Testing
<default_to_action> When testing multi-language/region support: 1. VERIFY translation coverage (all strings translated) 2. TEST locale-specific formats (date, time, currency, numbers) 3. VALIDATE RTL layout (Arabic, Hebrew) 4. CHECK character encoding (UTF-8, unicode) 5. CONFIRM cultural appropriateness (icons, colors, content)
Quick i18n Checklist: - All user-facing strings externalized - No hardcoded text in code - Date/time/currency formatted per locale - RTL languages flip layout correctly - Unicode characters display properly
Critical Success Factors: - Don't hardcode strings - externalize everything - Test with real speakers, not just translation files - RTL requires mirrored UI layout </default_to_action>
Quick Reference Card
When to Use
-
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
.kiro/skills/qe-localization-testing/SKILL.md