Text that never got translated
English buttons on a French page, raw translation keys like checkout.cta.label, and error messages that only exist in one language.
Use case
Localization testing in the app your customers actually use
Your translators can get every string right and the German checkout still shows a pound sign. Testavi's agents switch locale, go through your real flows and flag what a customer in that market would notice.
40%
of online shoppers say they will never buy from a website in another language.
CSA Research, Can't Read, Won't Buy, 2020. Survey of 8,709 consumers in 29 countries.
The same survey found 76% prefer to buy when product information is in their own language. So a half-translated page isn't a cosmetic problem. It's a shopper deciding your store isn't for them.
Most localization bugs don't come from bad translations, though. They come from everything around the text: a currency formatter nobody configured, a date shown the American way, a button label that's twice as long in German and wraps onto the price.
What the agents look for
Money in the wrong format
A £ in a euro cart, the wrong price list for a country, 1,000.50 where a German shopper expects 1.000,50.
Dates and addresses
Is 04/10 the 4th of October or April 10th? Depends who's reading. Same for address forms that reject a valid local postcode.
Layouts that don't survive longer words
German and French strings run longer than English. Buttons overflow, labels wrap onto prices, menus push content off screen.
Write the test once, run it per market
You don't need a separate test for every language. Describe the flow once and run it for each locale you sell in. Each run checks language, currency and formats for that market.
- 1Switch the store to Germany / Deutsch
- 2Add any jacket to the cart and open the cart
- 3Verify all visible text is in German
- 4Verify prices use € with a comma as the decimal separator
- 5Verify the delivery date is shown as DD.MM.YYYY
Where this fits next to Lokalise
They're often mentioned together, but they solve different problems. Lokalise and similar tools manage your strings and give translators screenshots and in-context previews so they know where text appears. That's a different job. They don't open your app and try to buy something. Testavi does the second part: it tests the live checkout, account and onboarding flows in each language once the translations have shipped.
| Translation management (e.g. Lokalise) | Testavi | |
|---|---|---|
| Job | Manage and translate strings | Test the localized app |
| Where it looks | Strings, screenshots, design files | Your running staging or production site |
| Catches | Translation quality | Missing text, wrong currency, formats, broken layouts, failing flows |
Based on Lokalise's documentation and in-context editing page, October 2026.
Questions
- Does it replace our translators?
- No. It makes sure their work shows up correctly in the product and that nothing around it breaks.
- Can it check checkout per country?
- Yes, including currency and regional pricing. See checkout flow testing.
- How do we start?
- With a free 30-day pilot. We write the first tests with you, and plans start at €299/month after that.
Protect your most important user flows
We write and maintain tests for your core flows during a free 30-day pilot. No credit card. Plans start at €299/month after that.