qa-test-i18n

Validate language switcher locale changes and detect untranslated strings on web pages.

Updated May 22, 2026
One-click install
npx skills add https://github.com/Luqman-Ud-Din/blackbox-qa-agent --skill qa-test-i18n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-test-i18n
Source: https://github.com/Luqman-Ud-Din/blackbox-qa-agent/tree/main/skills/qa-test-i18n
Command: npx skills add https://github.com/Luqman-Ud-Din/blackbox-qa-agent --skill qa-test-i18n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill verifies that a language switcher actually changes the visible interface and helps catch untranslated keys that leak through after localization changes.

Core Features & Use Cases

  • Language-switch validation: Confirms that switching locales produces a real UI text change instead of a no-op.
  • Untranslated key detection: Scans the page after a locale change for visible translation keys or template placeholders that should have been rendered.
  • Self-skipping behavior: Automatically returns no findings when a page has no language switcher, so it stays low-noise across mixed applications.
  • Use case: A multilingual product ships with an English/Spanish toggle, and this Skill can quickly reveal whether the switch updates labels, navigation, and content or leaves key strings exposed.

Quick Start

Run the qa-test-i18n skill on the current page to switch languages, compare visible text before and after, and report any untranslated strings.

Frequently Asked Questions about qa-test-i18n

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test a language switcher to ensure it changes the visible UI?

To test a language switcher, run an automated DOM inspection that switches locales, compares baseline text before and after the change, and confirms the visible interface updates rather than executing a no-op.

How do I detect untranslated keys and template placeholders after a locale change?

Untranslated key detection scans the page after a locale change to find visible translation keys or template placeholders that should have been rendered. It uses pattern detection to expose leaked strings.

What happens if I run i18n UI testing on a page with no language switcher?

If a page has no language switcher, the i18n UI test automatically returns no findings and skips execution. This self-skipping behavior ensures low noise across mixed applications.

Can I use untranslated string detection for multilingual web pages with native select dropdowns?

Untranslated string detection applies to multilingual web pages using native selects, dropdown switchers, and locale toggle controls during interactive desktop testing to verify localization changes.

What is the best way to catch broken translations in a multilingual web application?

The best way to catch broken translations is to automate locale switching, compare visible text before and after, and scan the DOM for untranslated key patterns that leak through after localization changes.