Internationalization & Localization Testing

What it is

Internationalization (i18n) testing proves the app can be localised: strings are externalised, encodings survive the round trip, and layout accommodates translated text. Localization (l10n) testing proves a specific translation is correct: locale formats, pluralisation, gender and region conventions.

1
source string ──▶ message catalog ──▶ rendered locale
2
    (en)              (vi, ar, ja)         + formats
3
                                    date · number · currency · plural

The high-risk areas are rarely the words themselves. They are the edges: right-to-left mirroring, text expansion (German and Finnish run long), Unicode normalisation, time zones, and languages with complex plural rules such as Arabic, Russian and Polish.

When to use it / when to avoid it

Use it for

Every release that ships more than one locale
New UI strings, especially those with placeholders, plurals or gender
Layouts that must mirror for right-to-left languages (Arabic, Hebrew, Persian)
Any flow involving dates, times, numbers, currency or sorting/collation

Avoid it when

The product is genuinely single-locale and will stay that way
You are duplicating a functional test only to change the language — check the format layer instead
The concern is pure encoding detection with no user-visible output

Frameworks & tools

Tool	Ecosystem	Notes
ICU MessageFormat	Multi	Plural, select and gender in one message syntax
CLDR / Intl	Multi	Platform-standard locale data for formatting
pseudo-localization	Multi	Fake locale to reveal unexternalised and hard-coded strings
i18next / i18n ally	JS/TS	Runtime i18n and editor-time missing-key linting
Babel / gettext	Python	Message extraction and catalog tooling
go-i18n / golang.org/x/text	Go	Locale-aware formatting and messages
Fluent	Multi (Rust, JS, Python)	Asymmetric localisation syntax for rich grammar
RTL screenshot diffing	Multi	Visual regression for mirrored layouts

Quick setup

1
npm install -D vitest
2
npm install intl-messageformat

1
import { IntlMessageFormat } from 'intl-messageformat';
2

3
new Intl.NumberFormat('de-DE').format(1234.5); // "1.234,5"
4
new Intl.DateTimeFormat('ja-JP').format(new Date()); // locale order

1
pip install babel

1
from babel.numbers import format_currency
2
format_currency(1234.5, "EUR", locale="de_DE")  # '1.234,50 EUR'

1
go get golang.org/x/text

1
NumberFormat nf = NumberFormat.getNumberInstance(Locale.GERMANY);
2
nf.format(1234.5); // "1.234,5"

1
using System.Globalization;
2
var de = new CultureInfo("de-DE");
3
value.ToString("C", de); // "1.234,50 €"

Example

1
const pr = new Intl.PluralRules('ar');
2
// Arabic has six plural categories
3
pr.select(0);  // "zero"
4
pr.select(1);  // "one"
5
pr.select(2);  // "two"
6
pr.select(11); // "many"

1
from babel.messages.catalog import Catalog
2
# Verify a catalog for each target locale parses
3
# and that plural forms exist for every count category.
4
for locale in ("en", "vi", "ar", "ru", "pl"):
5
    catalog = Catalog(locale=locale)
6
    assert catalog.locale is not None

1
import "golang.org/x/text/language"
2
import "golang.org/x/text/message"
3

4
p := message.NewPrinter(language.German)
5
p.Sprintf("%d", 1234) // "1.234"

1
@Test
2
void formatsPerLocale() {
3
  assertEquals("1.234,5",
4
    NumberFormat.getNumberInstance(Locale.GERMANY).format(1234.5));
5
  assertEquals("1,234.5",
6
    NumberFormat.getNumberInstance(Locale.US).format(1234.5));
7
}

1
[Fact]
2
public void FormatsArabicCurrency()
3
{
4
    var ar = new CultureInfo("ar-EG");
5
    var text = (1234.5).ToString("C", ar);
6
    Assert.Contains("ج.م", text); // EGP symbol
7
    Assert.True(ar.TextInfo.IsRightToLeft);
8
}

Anti-patterns & best practices

Never concatenate sentences from fragments. Word order differs per language; use full ICU messages with placeholders.
Test with pseudo-localization. A fake locale exposes hard-coded strings and text expansion before translators do.
Assert encodings explicitly. UTF-8 end to end; store and serve with the declared charset.
Test RTL as a first-class layout. Mirror the whole UI, not just flip the text direction.
Cover plural categories, not just one and many. Arabic, Russian and Polish have several forms.
Pin the time zone and locale in tests. Ambiguous environments produce false failures around dates.