Back to Blog
Blog

Localization Testing for Mobile Apps: How to Test Every Language

How to run localization testing for mobile apps: pseudolocales, text expansion, RTL, dates and currency, language vs region vs IP, and automated runs per locale.

Written by
Gautam Agarwal
Read time
11 min read
Published
Localization Testing for Mobile Apps: How to Test Every Language

Quick answer: localization testing checks that your app works and reads correctly in every language and region you ship, by running real journeys with the device set to each locale and checking text, layout, right to left mirroring, dates, numbers, currency, time zones and location based behavior. Translation files prove the words exist. Localization testing proves they fit, read in the right direction and sit beside the right formats.

A translated app is the same person in a new suit. The person stays the same, yet the fit changes everywhere: sleeves run long in German, buttons swap sides in Arabic, and the price tag switches currency. Localization testing is the fitting session.

Key Takeaways

  • Start with pseudolocalization: Android's en-XA and ar-XB pseudolocales and Xcode's pseudolanguages expose truncation, hard coded strings and right to left bugs before any translation exists.
  • Language, region and IP address are three separate settings: language changes the words, region changes formats, time zone and location, and IP changes what your servers see.
  • Test at least one long language, one right to left language and one non Latin script, plus your top revenue markets.
  • Check formats with real journeys: dates, numbers, currency, plurals and reminders that depend on the time zone.
  • BugRadar opens the app in any language and region from the first screen, while your test steps stay in English.

What is localization testing?

Localization testing verifies that a localized app behaves correctly for users in a specific language and region. It sits on top of internationalization, the engineering work that makes localization possible: strings in resource files, layouts that stretch, and formatters that follow the locale.

What can break in a localized app

AreaWhat can break
StringsHard coded English text survives in a translated build
Text lengthLonger translations truncate, wrap badly or push buttons off screen
DirectionRight to left languages keep left to right layouts, icons and swipe directions
FormatsDates, numbers, currency and plurals follow the wrong country
Scripts and fontsCharacters render as boxes, or line heights clip accents
InputNames, addresses and phone numbers in local formats fail validation
Region logicTime zones, prices and location based features use the wrong country
Notifications and emailsMessages arrive in English, or at the wrong local time

Language vs region vs IP address

Most localization bugs come from mixing up three settings. BugRadar's language and region docs separate them clearly:

SettingWhat it changesExample
LanguageThe words your app showsGerman UI text
RegionDates, numbers, money, time zone and device locationen-MX: English text with Mexican formats, time zone and location
IP addressThe country your servers seeA pricing API that returns Mexican pesos

Any language works with any region, so English with Mexico as the region is a real and useful test case. A language alone leaves the IP address unchanged; country specific server responses need a proxy location.

__wf_reserved_inherit

Ways to run localization tests

MethodWhat it provesWhat it skips
PseudolocalizationTruncation, hard coded strings and RTL layout, before translationReal translation quality
Native speaker reviewMeaning, tone and cultural fitRepeating on every build
Screenshot review per localeVisual breakage across many screensBehavior, such as formats inside a flow
Code based tests with language and locale settingsJourneys in each locale, in codeLocators that change with each translation
BugRadar runs per language and regionJourneys in each locale, with steps written once in EnglishTranslation quality judgments

Start with pseudolocalization

Android

The Android pseudolocales guide describes two built in pseudolocales:

  • English (XA) adds accents, expands text and brackets each message, which exposes truncation and messages split into pieces
  • AR (XB) switches messages to right to left and reverses their characters, so you can test a right to left layout using only English text

Enable them in debug builds, then pick one in the device's language settings; this guide to Android emulator setup covers getting an emulator ready first:

android {

    buildTypes.getByName("debug") {

        isPseudoLocalesEnabled = true

    }

}

Text that stays plain English in a pseudolocale points to strings hard coded outside your resource files.

iOS

For how native iOS and Android suites fit around this, see this guide to native mobile app testing. Xcode offers pseudolanguages for the same job, including a double length pseudolanguage for text expansion and a right to left pseudolanguage. Apple's guide to preparing your interface for localization covers them alongside layout advice. Its companion page on testing localizations when running your app covers running each language and region you support.

__wf_reserved_inherit

The localization test checklist

CheckLocale to useWhat to verify
Every main screenA pseudolocaleZero hard coded strings, zero truncation
Long textGerman (de-DE)Buttons, tabs and table headers fit
Right to leftArabic (ar-SA)Layout, icons, swipe gestures and progress bars mirror
Non Latin scriptJapanese (ja-JP) or Chinese (zh-TW)Characters render and line heights fit
Dates and timesen-GB vs en-USDay and month order, 12 or 24 hour clock
Numbers and currencyde-DE, pt-BRDecimal separators and currency symbols
PluralsYour top languages"1 item" and "5 items" use the right forms
Time zone logicA region far from your serversReminders and deadlines fire at local time
Location logicEach launch countryStore, shipping and content options match the country
CheckoutEach paid marketPrices, taxes and payment methods match the market
NotificationsEach languagePush and email copy arrive translated, at local hours

How to automate localization tests with BugRadar

Choose a language and region per run

With BugRadar: pick Language and Region in the run dialog or the automation editor. Your app opens in that language from its first screen on Android, iOS and web; on web, your site sees the language in the Accept-Language header and in navigator.language.

From the CLI:

BugRadar flows run --flow checkout --locale de-DE

From the GitHub Action:

```yaml

    locale: de-DE

```

‍

With BugRadar: the Runs API, build uploads and MCP run tools take a locale value too, and an upload's language applies to every run it starts, including later pull request runs against that build.

Keep your flows in English

With BugRadar: test steps stay in English. BugRadar tells the agent the run's language, so a step such as "Tap Sign in" finds Anmelden on a German screen. Text a step asks the agent to type is typed exactly as written, so put German input in German.

Tap Sign in.

Sign in as ${env:DE_TEST_USER}.

Add the first product to the cart.

Verify the total uses euros with a comma as the decimal separator.

Know what each platform changes

With BugRadar:

  • choosing a language or region also moves the device's GPS location to that country on web, Android and iOS
  • the time zone follows the country on web and Android Emulators, while iOS runs keep US Pacific time
  • on a physical iPhone, and on an iOS Simulator on your own machine, only your app switches language
  • leaving both pickers on Default runs in US English (en-US), and the next run after a language change starts in US English again
  • runs are cached per language, so a German run only replays steps recorded in German

Switch language mid journey

With BugRadar: to test a language switch inside a flow, write it as a step, such as "Set the device locale to de_DE". An unsupported locale code is refused before the run starts with an Unknown locale error, and a device that refuses a language fails the run before the first step.

Build a locale matrix

Running every flow in every language is expensive. A practical matrix:

TierLocalesWhen to run
Every pull requestYour main languageEvery change
NightlyOne long language, one RTL language, one non Latin scriptScheduled automation
Before releaseEvery shipped language and paid marketRelease candidate

With BugRadar: set a language and region on each automation, so a nightly German run and a nightly Arabic run sit side by side on a schedule.

Localization testing examples

Each example starts from a failing run and traces it to a cause and a fix.

Example 1: The German checkout button is cut off

StepExpectedWhat the de-DE run showed
Add a productCart badge shows 1Cart badge shows 1
Open the cart"Zur Kasse gehen" button"Zur Kasse..."
Tap the buttonCheckout screenCheckout screen, label still cut

Cause: the button had a fixed width sized for "Checkout".

Fix: let buttons grow with their text, and run the English (XA) pseudolocale on every screen before translations land.

Example 2: The back arrow points the wrong way in Arabic

StepExpectedWhat the ar-SA run showed
Open a productRight to left layoutRight to left layout
Look at the back buttonArrow points rightArrow points left
Swipe to go backSwipe follows the mirrored layoutSwipe direction unchanged

Cause: the arrow was a fixed image and the gesture was hard coded for left to right.

Fix: use direction aware icons and gestures, and keep one right to left locale in the nightly matrix.

Example 3: British users see American dates

StepExpectedWhat the en-GB run showed
Book a slot on 3 AprilConfirmationConfirmation
Read the booking date03/04/202704/03/2027
Read the reminder email3 AprilApril 3

Cause: the date format string was hard coded as month first.

Fix: format dates with the platform's locale aware formatter.

With BugRadar: run the same booking flow with English as the language and the United Kingdom as the region; any language works with any country.

Example 4: A reminder fires at the wrong local hour

StepExpectedWhat the Android es-MX run showed
Set a reminder for 9:00Saved for 9:00 localSaved
Check the scheduled time9:00 Mexico City time9:00 server time
Wait for the reminderFires at 9:00 localFires two hours late

Cause: the app sent the reminder time to the server as a bare clock time, dropping the device's time zone.

Fix: send times with their time zone, or as UTC with the user's zone stored.

With BugRadar: a Mexico region run moves the time zone to Mexico City on Android Emulators and web, so this bug shows up in a normal flow.

Common localization testing problems and fixes

ProblemWhat to check
English text inside a translated buildHard coded strings; run a pseudolocale
Region looks right, server responses look AmericanIP based logic; add a proxy location
iOS run shows the wrong time zoneiOS runs keep US Pacific time; test time zone logic on Android or web
A run fails before the first stepAn unsupported locale code, or a device that refused the language
Typed text appears in English on a German runTyped text stays exactly as written; write it in German

The localization testing process, summarized

StepWhat you doOutput
1. PrepareMove strings to resources and use locale aware formattersAn internationalized app
2. PseudolocalizeRun en-XA, ar-XB and Xcode pseudolanguagesLayout and string fixes before translation
3. TranslateShip translations with screenshots for contextLocalized builds
4. AutomateRun journeys per language and regionLocale coverage on a schedule
5. ReviewHave native speakers read key screensNatural, correct copy
6. ReleaseRun every shipped locale on the release candidateA confident global release

Conclusion

Localization testing proves that every user sees an app made for them: words that fit, layouts that read in their direction, and dates, prices and reminders that match their country. Start with pseudolocales, separate language, region and IP in your thinking, and run real journeys per locale on a schedule.

A good first step this week: enable Android pseudolocales in your debug build, then run your checkout flow in BugRadar with de-DE and ar-SA. For notification copy per language, see the guide to push notification testing; for where emulators fit, this guide on emulators vs real devices; for Flutter apps, this guide to Flutter integration testing; and for a wider view of tools, this ranking of mobile app testing tools.

__wf_reserved_inherit

FAQs

What is localization testing for mobile apps?

It checks that the app works and reads correctly in every language and region you ship.

What is pseudolocalization?

Fake translations that lengthen, accent or reverse text to expose layout and string bugs early.

Which languages should you test first?

One long language, one right to left language, one non Latin script, plus top markets.

What is the difference between language and region?

Language changes the words; region changes dates, numbers, money, time zone and location.

Do BugRadar flows need translating?

Steps stay in English, and the agent finds the translated text on screen.

How do you test country specific prices?

Set the region for formats, and add a proxy location when servers price by IP address.

‍

‍

Fix bugs, not tests.

Talk to an expert.

Book 30 minutes with our team. We'll show you BugRadar running on your app.

Start building.

Describe a user journey and watch an agent run it on iOS, Android, and web.

Try for free