For teams with a translated web app who want to know what breaks in each language.
Your setup
- A web app on staging in English, German and Japanese.
- The language is picked by a switch in the app, by the URL (
/de/), or by the user's profile.
Say this to Certyn
Check checkout and account settings on staging in German and Japanese. Our language switch is in the footer. File missing translations, cut-off text and wrong date or price formats.
What Certyn does
- Asks how your app picks the language, if you did not say. Certyn cannot change the browser's own language, so this decides the path. It can keep the answer as a memory.
- Says the run length and starts an explore run with your pages and languages in the goal (
app.run.createtypeexplore). - Switches the language your app's way: the switch, the URL, or a test account set to that language (see the recipe on roles).
- On each page, looks for text left in English, raw keys such as
checkout.title, placeholders such as{name}orundefined, and broken characters. - Looks for text cut off or overflowing buttons, menus and tables, also at a phone size (
browser.device.set). - Checks dates, numbers and prices in the local format, for example
20.10.2026and1.234,56 €in German. If you support Arabic or Hebrew, it checks the right-to-left layout. - Files one issue per real bug, with the language, page and a screenshot.
What you get
- Issues by language and page, with screenshots.
- A run report with each language and page checked.
Limits
- Runs cannot set the browser's language (
Accept-Language). If your app takes the language only from the browser, a run sees the default. Add a URL parameter or a setting for testers. Or Certyn runs a short Playwright script on its Machine with a locale such asde-DEand checks the text. It does not see that script's screen, so layout is checked only by element sizes. - Dates and numbers that follow the browser's language show the default format in runs.
- Certyn finds clear mistakes. It is not a native speaker review of tone and meaning.