Localization quality assurance (LQA) is still a top priority for video game companies, which also makes it a hot topic for us at Game Global. At the last Game Global Digital Summit, we had the pleasure of having Mike Souto, Business Development Director at Gridly , and Ville Lehtinen, Senior Developer at Rovio Entertainment, present about how to streamline the LQA process. This article will delve further into the best practices for processes and automation.
What is LQA?
Localization quality assurance (LQA) is the last stage in the game localization process. Primarily, it focuses on linguistic testing and translation quality review but also covers UI/UX evaluation, compliance testing, culturalization, internationalization, functional tests, and more.
In short, during LQA, native-speaking linguists with expertise in gaming and local culture play and review your game, making sure that there are no errors or problems — both linguistically and visually.
If the game is about to be published in multiple languages, every version should be tested by the appropriate native professional.
Which LQA process is right for your game?
Even though globalization managers usually focus on linguistic testing and translation quality review, localization QA can also involve UI/UX evaluation, functional, or compliance testing.
Naturally, the more the project can cover the better, but there’s a cost. The cost is deeply influenced by the performance of the localization testing process. For example, resources needed for checking the text in a spreadsheet will be significantly lower compared to running full-functional testing of the latest build for a recently released title.
Likewise, the product under assessment itself vastly influences how we execute the QA testing process. Consider the difference in sending testers a simple link to start their job as opposed to them having to spare 16 GB of their hard disk and go through a 20-minute installation!
The need for unified processes and automation
LQA streamlining is based on several key factors:
● Unifying the stages of the LQA process
● Connecting the LQA process to the product itself
● Managing stakeholder collaboration
As a comprehensive localization management system for video games, Gridly has specifically focused on unifying the stages of the LQA process.
For our LQA team, we need an interface where testing occurs and a place where results and issues are logged and processed. When these two interfaces are separate, then testers will need to switch back and forth. Our testing process will take longer, and there’ll be potential for drop-outs or miscommunication.
Unifying testing and issue processing in one environment would mean testers can log everything instantaneously without the need to switch. Therefore, if our product or technology allows, Gridly can be a great first step to streamline your project.
Localization QA testing using screenshots
By using a combination of texts and screenshots (or even sounds and videos), Gridly merges the linguistic and visual testing, while allowing you to perform at high speed and reasonable budget.
This is particularly useful when we talk about app, mobile and game testing: not only is it faster to check text and a related screenshot and move on to the next one, it also helps with situations taking some time to reproduce when performing live testing.
How does it work?
As Mike and Ville thoroughly illustrated during the latest Game Global Digital Summit and in this article, Gridly makes it possible to import source text and screenshots directly from Unity. Check out the recap below!
Want to know more?
You will find the complete guide to winning at LQA projects here, including a case study on how Rovio streamlined localization QA testing for Small Town Murders with a demo of screenshot LQA in Gridly.
We are happy to hear your thoughts and further comments below.
Have more LQA stories to share?
Don’t miss your opportunity to present at our next event, happening in Berlin, Germany, on July 11, 2022. SUBMIT YOUR PROPOSAL NOW!