This blog lists out some localization testing best practices and tips based on experience we have collected over the years. Localization Testing Best PracticesIn executing many localization testing projects over the years, we've developed a checklist of best practices that we use for every localization testing project and continue to update as we gain more experience.
For agile testing, the more testers know, the better. With more relevant information and knowledge, agile testers can be sensitive to potential issues and therefore be able to provide more efficient feedback on an agile project.Although implicit, most agile testers serve to bridge the product team’s expectation and actual development work. In this sense, agile testers play a critical role, especially when they possess valuable knowledge and skills to understand developers and product owners from different points of view. But to do this requires skills that are not common to many ‘traditional’ testers. What do these ‘agile testing’ skills include?
XBOSoft Published its 2013 Mobile Testing Report From November 2012 to February 2013 we conducted a [...]
Localization testing is a necessary part of the development life cycle of any application with international aspirations.
With the economic down turn in many parts of the world, it often makes business sense to lower risk and sell an application in different language areas. However for us in QA delivering software in multiple languages creates another type of risk: the risk of localization defects.
In order to help testers that are new to localization testing (or for old hands that wants to refresh their memory) this post lists the 10 most common types of localization defects, explains their root causes and provides ideas to prevent them.
Defect reports are among the most important deliverables to come out of software testing. The point of writing a defect report is to get defects fixed. Hence, it is worth the effort to learn how to write good defect report. Characteristics of a good defect report include:Reproducible: make it easy to reproduce the defect by developerMake sure you include the environment, data used, and all steps necessary to reproduce the defect. If your defect is not reproducible it will never get fixed, and the defect may be considered INVALID! Developers may complain when they cannot successfully reproduce a problem, so the steps should be clear and precise. Do not assume or skip any key steps.Specific: be specific and to the pointTry to summarize the problem concisely yet in effective way.
Large companies have been localizing their products for a long time. Now, smaller and medium size companies are attacking international markets trying to grow revenue away from home, especially with the proliferation of web-based software. When you release a multiple language supported product, not only does it have to be localized in the target language, it also needs localization testing. To conduct localization testing, you need test all the different localized versions of your product. You probably don't have the time and resources to cover all the languages, so you have to focus and prioritize. How to set the priorities then?