To test or no to test. That is the (rare) question. While it’s quite obvious that
a software product has to undergo a quality review before its release, the extent to which the product needs to be tested isn’t always so clear.
Precise functional testing is not enough to assure top-notch quality. Flawless language used in your software product is equally important as proper functioning. It goes far beyond checking whether any translation is missing, texts are cut off or the context is incorrect. It’s about the comfort of your target users and clear communication of the product functionalities.
If the localised version works, it doesn’t mean that the product is ready to be released. Pushing the linguistic layer to the background results in all kinds of consequences. And an accidental message in other language, like the one below, is just the tip of the iceberg.
Functionality may well be the number one priority when it comes to localisation. But the same effort and time that is put into functional testing should also go into linguistic testing. This is how the target users get the impression that the product is specifically developed for them, with clear instructions, correct texts and attractive user interface. Properly displayed text with transparent notifications, commands or option names may even mitigate the effects of slight functional issues.
So, do test your product two, three times or more, making sure that all language issues have been resolved effectively. Show your users you care about them, no matter where they live and what language they use.