Detecting translation and localization bugs in your product’s interface
We perform localization testing of games and applications for iOS, Android, Windows, and MacOS. We can also test localizations of console games and websites.
We look for strings that are still in the source language
We look for grammatical mistakes, incorrect word order, erroneous use of commas, etc
We look for flaws in the way characters such as diacritic marks or ideograms are displayed
We look for text that doesn’t fit on buttons and other UI errors
We check whether length, weight, and other units of measurement are displayed correctly for the target language
We verify whether jokes, dialogues, and other elements that add color to a game or application have been translated in the same style
We look for places where the same item, character, or function is referred to in different ways in the translation
A translator who is a native-speaker of the target language installs a localized build and launches the software on their device.
If you are unable to give the translator access to such a build, we request that you take screenshots of all screens from the localized version of your product. In this case, our translators will evaluate the quality of the localization based on the screenshots.
The cost of localization testing depends on the number of hours spent on the testing process. The rates below are in US dollars per hour spent by a specialist.
Language | Hourly rate |
---|---|
Afrikaans | 63.3 |
Albanian | 43.2 |
Amharic | 43.3 |
Arabic | 43.3 |
Arabic (Egypt) | 43.3 |
Arabic (Morocco) | 43.3 |
Armenian | 33.3 |
Azerbaijani | 43.3 |
Basque | 63.3 |
Belarusian | 33.3 |
Our localization quality testers are linguists with experience in localization testing of particular software products. They are usually trained as such on our projects and have a successful record of similar tasks. We always select professionals with the top translation quality scores and best client references.
If an app, game, website, or other software is localized, the localized build or beta version is usually tested for functionality bugs by the client testers. However, while functionality bugs (if any) may be minor, in the case of a dedicated localization integration, linguistic errors are omitted during the standard testing process. That’s why localization (or linguistic) testing is needed.
Generally speaking, localization testing is a part of the software testing process that ensures the quality of the localized texts within the context, i.e., in the product interface.
Sometimes, linguistic testing is performed separately from software testing, but it can also be a part of the same test case.
This is mostly a question of terminology. The previous answer explains that linguistic testing is about controlling the language localization of a product in context, meaning texts within the UI (app screens, messages, and notifications).
In some companies, localization testing is the same as linguistic testing, whereas others prefer to include into localization testing the functionality testing of the product. In this case, localization testers are required to report not only linguistic errors and inconsistencies but also functionality bugs.
While testing is typically linear for websites, functionality testing for software and apps usually covers a brunchy decision tree and requires test scenarios and cases.
We usually discuss the scope of the required testing activities with the client. The client provides our specialists with context (localized screenshots, Figma screens, or other dedicated professional testing apps). If the client prefers that our specialists also perform functionality tests, we will discuss the test case.
In either case, our localization testers report any bugs that are revealed in addition to linguistic errors.
In order to perform localization testing internally, the company first needs dedicated staff: localization professionals with localization testing experience.
While localization testing reveals linguistic errors and software testing reveals functionality errors, these two types of tests usually require different skill sets.
Moreover, not all professional linguists can perform localization testing, write linguistic test cases, or work with dedicated testing tools.
Besides, it’s generally recommended that linguistic testing be performed by a separate linguist than the one who performed the initial localization.
All of these factors make it quite challenging to perform linguistic testing in-house, with most of our clients preferring to outsource this task to professional localization testers.
Upon request, our linguistic testers can work with various design, testing, and project management tools, including Figma, Jira, Asana, Trello, TestFlight for iOS product testing, BrowserStack, and other bug reporting tools and software.
We translate into more than 100 languages, including the most popular (English, Chinese, Japanese, German, French, Spanish), and rarer ones, and even dialects. Please, request a quote to get an estimate of your project.
We can find a translator in almost any language that the client needs, depending on his product and goals. Sometimes localization into niche languages can offer better prospects than localization into mainstream languages.
In case some rare language is not on the list, we can help with searching and recruiting linguists.
We can't wait to work with you!
We have localized over 1,500 projects and produced 1,000+ videos. Let's make something special for you too!
We’d like to learn more about it. In return, we’ll get back to you with a solution and a quote.