Internationalization (i18n) Testing Services | QAonTOP Skip to main content
QAonTOP
Contact Us

Internationalization Testing Services

Adding a new language should mean adding translations, not rebuilding screens, fixing data and chasing hard-coded text.

We check that your product is built to work in any language, script and region: text out of code, Unicode end to end, formats driven by locale and layouts ready for longer and right-to-left text. Problems get fixed once, before they are copied into every market.

  • Before translation starts
  • Pseudo-locales
  • Code-level fixes
  • Free one-week POC

[ Why internationalization testing ]

Fix it once in the code, not again in every language

Many products are built for one language and one country, then stretched to fit others. That is when the problems appear: text glued into code, dates fixed to one format, a database that mangles accented names, layouts that only fit English. Each issue is then repeated in every new language. Internationalization testing finds these weaknesses in the foundations, while they are still cheap to fix.

Ready to test translated versions? See localization testing →

01

Every new language costs less

Fix the foundations once, then add languages without rework.

02

Faster market launches

Translations drop in without layout or code surprises.

03

Data that travels

Names, addresses and content in any script, stored and shown correctly.

04

Fewer locale bugs

Formats, time zones and sorting handled properly from the start.

What “i18n-ready” looks like

Six foundations we check before you add another language.

Strings

All user-facing text in resource files, none in code

Encoding

UTF-8 end to end, from UI to database and files

Formats

Dates, numbers and currency from the locale, not hard-coded

Layout

Flexible widths and wrapping for longer text

Direction

Logical layout properties ready for right to left

Time

UTC storage, local display, daylight saving handled

[ What we test ]

Eleven checks for a product that’s ready for the world

From code that keeps text separate to data that handles every script. Each one lists what we check, when you need it and the problem it prevents.

i18n code & architecture review

Built for any language

We review how your product handles text, formats and regions in code, so problems are fixed once, not language by language.

What we check
  • Text kept out of code and in resource files
  • Locale handling in front end, back end and database
  • Use of standard libraries such as ICU and i18next
  • Risks ranked with practical fixes for your stack
When you need it

Before adding your second language, or before a major expansion.

The problem it preventsRewriting the same screens for every new language

Hard-coded string detection

Nothing left behind

We find text that is written directly into code, templates, images or emails, where translators can’t reach it.

What we check
  • Hard-coded text in UI, emails, PDFs and error messages
  • Text inside images and icons
  • Strings built by joining fragments
  • Untranslatable dates and units in code
When you need it

Before translation starts, and on every release.

The problem it preventsEnglish words showing up in an otherwise translated product

Pseudo-localisation testing

Find problems before translation

We switch your product to a fake language that is longer, accented and marked, so layout and code issues appear before real translation.

What we check
  • Longer text to expose truncation and fixed widths
  • Accented and non-Latin characters to test fonts
  • Markers that reveal hard-coded and joined strings
  • Right-to-left pseudo-locale for bidirectional checks
When you need it

Early in development, and before each new language.

The problem it preventsPaying for translations, then finding the product can’t display them

Unicode, encoding & character sets

Every script

Names, addresses and content come in every script. We check that your product stores, shows and sends them correctly.

What we check
  • UTF-8 handling end to end: UI, APIs, database, files
  • Accents, Cyrillic, Arabic, Chinese, Japanese, Korean and emoji
  • Imports, exports, CSV and PDF generation
  • Emails, SMS and notifications with special characters
When you need it

For any product with user names, addresses or content.

The problem it preventsCustomer names turning into question marks or broken symbols

Locale-aware formats

Dates, numbers, currency

We check that dates, times, numbers, currencies and units follow the user’s locale instead of being fixed to one format.

What we check
  • Date and time formats per locale
  • Decimal and thousands separators
  • Currency symbols, placement and rounding
  • Units, phone numbers and postcodes
When you need it

Before launching in any new region.

The problem it preventsPrices, dates or quantities that are misread by local users

Text expansion & layout flexibility

Room to grow

Translated text is often longer than English. We check that layouts stretch and wrap gracefully instead of breaking.

What we check
  • Flexible widths in buttons, menus and tables
  • Wrapping and truncation rules
  • Line height for scripts with tall characters
  • Responsive layouts with long text on mobile
When you need it

Before translation and after UI redesigns.

The problem it preventsA UI that only works in English

Right-to-left readiness

Bidirectional support

Arabic, Hebrew and other right-to-left languages need a mirrored interface and correct mixing of text directions.

What we check
  • Layout mirroring using logical CSS properties
  • Icons and images that should and shouldn’t flip
  • Mixed right-to-left and left-to-right text
  • Form fields, numbers and cursor behaviour
When you need it

Before supporting any right-to-left language.

The problem it preventsAn expensive rebuild when you add Arabic or Hebrew

Time zones & calendars

Right time, everywhere

Events, deadlines and reports must show the right time for every user, including daylight saving changes.

What we check
  • Storage in UTC and display in local time
  • Daylight saving transitions
  • Week start, holidays and different calendars
  • Scheduling across time zones
When you need it

For bookings, scheduling, reporting and anything with deadlines.

The problem it preventsMeetings, bookings or reports off by an hour or a day

Sorting, search & input methods

Works with every language

Sorting, searching and typing behave differently across languages. We check they work for your target markets.

What we check
  • Alphabetical sorting rules per language
  • Search with accents, case and different scripts
  • Input method editors (IME) for Chinese, Japanese and Korean
  • Keyboard layouts and on-screen keyboards
When you need it

Before launching in markets with different scripts.

The problem it preventsUsers who can’t find their own name in a sorted list

Multi-currency & multi-region data

Global by design

Products used in several regions need data models that support many currencies, tax rules and regional settings.

What we check
  • Multiple currencies and exchange-rate handling
  • Regional tax, pricing and invoicing rules
  • Region-specific content and settings
  • Data residency and regional configuration
When you need it

For e-commerce, finance and SaaS products serving several regions.

The problem it preventsData structures that can’t support your next market

i18n checks in CI

Every build

Automated checks in your pipeline catch hard-coded strings, missing keys and pseudo-locale layout issues on every change.

What we check
  • Missing and unused translation keys
  • Pseudo-locale runs on key screens with Playwright
  • Locale and time zone emulation in tests
  • Rules agreed with your team to keep noise low
When you need it

Once your product supports more than one language.

The problem it preventsNew hard-coded text slipping in with every release

[ Internationalization vs localization vs translation ]

Build it ready, then make it local

Internationalization comes first. Here is how the three fit together, and what a pseudo-locale finding looks like.

Question it answersWhen and how
Internationalization (i18n)Is the product built to support any language and region?During development, in code and pseudo-locales
Localization (L10n)Does it work and feel right in this specific market?After translation, with native speakers
TranslationAre the words correct?Before or during localisation, by translators
Sample pseudo-locale findingHigh
Locale
Pseudo-locale (expanded, accented)
Screen
Account settings
Issue
“Save changes” shown in plain English: string is hard-coded in the component
Also
Date shown as 03/04/2026 in every locale; format fixed in code
Impact
High · will appear untranslated in every new language
Fix
Move text to resource file; format dates with Intl / ICU

Example only. Real findings come from your own product.

[ How we work ]

Six steps to a product that’s ready for any market

We start with the foundations, prove them with pseudo-locales and keep them healthy in CI.

  1. Step 1 of 6

    Understand your stack

    Frameworks, libraries, languages today and where you plan to go.

    You getStack and target review
  2. Step 2 of 6

    Review the foundations

    Code, data and architecture checked for i18n readiness.

    You getReadiness report
  3. Step 3 of 6

    Run pseudo-locales

    Expanded, accented and right-to-left pseudo-locales across key screens.

    You getPseudo-locale findings
  4. Step 4 of 6

    Test the edge cases

    Unicode, formats, time zones, sorting and input methods.

    You getIssue log with fixes
  5. Step 5 of 6

    Fix and retest

    Developers fix; we retest and confirm.

    You getRetest results
  6. Step 6 of 6

    Guard it in CI

    Automated i18n checks so new issues don’t creep in.

    You getCI checks
  • Free one-week POCA pseudo-locale run and readiness check on your key screens.
  • Fixes for your stackPractical guidance for the frameworks and libraries you already use.
  • NDA before accessWe sign your NDA before we see any code.

[ Tools ]

The tools behind our internationalization testing

12 tools across four jobs, matched to your stack.

Libraries & standards

How good i18n is built.

02 TOOLS
  • ICU / CLDRLocale data and formatting
  • i18next / FormatJSi18n libraries for JavaScript

Localisation platforms

Where strings live.

04 TOOLS
  • LokaliseTranslation management
  • CrowdinLocalisation platform
  • PhraseTranslation management
  • Microsoft Pseudo-localesFake locales for testing

Testing & inspection

Emulating any locale.

04 TOOLS
  • PlaywrightLocale and time zone emulation
  • Chrome DevToolsLocale and time zone overrides
  • BrowserStackReal devices by region
  • SonarQubeCode checks

Management

Plans, issues and results.

02 TOOLS
  • JiraIssues and fixes
  • TestRaili18n test runs

See every tool we use on our technology stack page →

[ Case Studies ]

Products our QA engineers have worked on

Each one links to the full write-up by the engineers who ran it. Bilingual English and French support was part of our work for Supply Ontario; the others show our wider QA work.

All case studies →

[ Ways to work ]

Six ways to get internationalization testing done

A readiness review before expansion, checks every sprint, or help preparing your next language.

Not sure which fits? Find your model in four questions or compare all six.

[ FAQ ]

Internationalization testing questions, answered

{{ f.a }}

[ Contact us ]

Get an i18n readiness check for your product

✓ Free one-week POC✓ NDA before access✓ A QA lead replies the same day

[ Keep exploring ]

Other testing services

All services →