localization-testing
This skill systematically audits your application's internationalization layer to catch untranslated content and locale-specific gaps before deployment. It integrates with Claude Code to scan codebases for hardcoded strings and verify that all user-facing text has proper translation coverage across your supported languages.
localization-testing systematically audits your application's internationalization layer to identify untranslated content and locale-specific gaps before deployment. It integrates with Claude Code to scan codebases for hardcoded strings and verify that all user-facing text has proper translation coverage across your supported languages, catching strings that should have been externalized for translation but remain embedded in your code.
AI-generated summary based on this skill's SKILL.md
Install
proffesor-for-testing/agentic-qe/localization-testing · repository language: TypeScript
git clone https://github.com/proffesor-for-testing/agentic-qe
cp -r agentic-qe/.claude/skills/localization-testing ~/.claude/skills/localization-testingFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How does localization-testing help validate translation coverage and detect missing or hardcoded strings?
localization-testing systematically audits your application's internationalization layer to identify untranslated content and locale-specific gaps before deployment. It integrates with Claude Code to scan codebases for hardcoded strings and verify that all user-facing text has proper translation coverage across your supported languages, catching strings that should have been externalized for translation but remain embedded in your code.
What locale-specific formatting does localization-testing validate across different languages?
localization-testing tests locale-specific formatting for dates, times, currencies, and numbers to ensure they display correctly according to regional conventions. This prevents formatting errors where, for example, a date formatted as MM/DD/YYYY in the US would appear incorrectly in regions expecting DD/MM/YYYY, or currency symbols and decimal separators appear in their proper locale-appropriate positions.
Can localization-testing verify RTL language layouts and visual rendering for Arabic, Hebrew, and similar languages?
Yes, localization-testing includes verification of RTL (right-to-left) language layouts and visual rendering for Arabic, Hebrew, and similar languages. It validates that UI elements, text flow, and component alignment properly adapt to RTL directionality, ensuring your application displays correctly without text overlap, reversed button placement, or other layout issues specific to right-to-left writing systems.
How does localization-testing ensure Unicode character support and proper encoding across all supported languages?
localization-testing assesses Unicode character support and proper encoding across all supported languages to prevent character display issues, mojibake (garbled text), or missing glyphs. It validates that your application correctly handles UTF-8 and other character encodings, ensuring that special characters, diacritics, and language-specific symbols render accurately regardless of the user's locale.
What role does localization-testing play in assessing cultural appropriateness for new market launches?
localization-testing evaluates the cultural appropriateness of content, icons, and colors for new market launches, helping you identify potential cultural mismatches or offensive imagery before deployment. This proactive assessment reduces the risk of market rejection or brand damage by catching culturally insensitive elements early in the localization process.
What are the best practices for international app testing that localization-testing supports?
localization-testing supports international app testing best practices by providing a comprehensive framework that covers translation validation, locale-specific formatting checks, RTL layout verification, Unicode encoding validation, and cultural appropriateness assessment. It enables systematic quality assurance across multiple languages and regions, helping teams catch localization defects early and maintain consistent user experience globally.
SKILL.md
rendered from the published skill — quoted content, verbatim
Localization & Internationalization Testing
Browser engine
Browser-driven locale checks (RTL layout diffs, language-switching flows, locale-specific screenshots) should go through the qe-browser fleet skill. Example:
```bash vibium go "$BASE_URL?lang=ar" # Arabic, RTL vibium wait load node .claude/skills/qe-browser/scripts/visual-diff.js --name homepage-ar-rtl vibium go "$BASE_URL?lang=ja" # Japanese, CJK text
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 4 files
.claude/skills/localization-testing/SKILL.md
.claude/skills/localization-testing/evals/localization-testing.yaml
.claude/skills/localization-testing/schemas/output.json
.claude/skills/localization-testing/scripts/validate-config.json