Over the past few months, Globalme conducted two speech-related data collection projects in China. In one project we invited 600+ native Mandarin speakers to come…
Last weekend we did a guest post for VentureBeat comparing Siri, Cortana and Google Now in five different languages – English, French, Italian, German and Mandarin. We…
Perhaps I should have titled this post “Tools to Assist Localization Testing” as I don’t think there is a tool developed particularly for localization testing. However, since Localization Testing has such a broad definition, one needs a broad set of tools to do the job efficiently. Obviously the tools that need to be used for web localization testing vs. documentation review will be different, and some tools will only apply to particular roles. Localization Engineers do more automation while Localization Testers typically focus on reporting.
Software usability testing is great for generating lots of data. If you take that data and feed it back to your developers, you’ll get an improved product, and that’s great. It’s the most important reason for testing.
But if you’re going to invest in testing, then you can, and should, try to get more.
If you’re just starting to investigate the localization process, absorbing all of the new concepts can be overwhelming. One question I hear a lot is: What exactly is the difference between localization and internationalization?
If this is new terminology, localization and internationalization might feel like twins. In reality the two are not all that similar. So let’s clear up any confusion with some simple definitions.
If you’re new to usability testing, the information available can be very technical and kind of confusing. It’s hard to know what you’ll need to invest, and what you can expect to get out of it at the end. One of the most important questions to answer is: What kinds of information should you get from your testers? Here are some ideas to get you started.
When you work with an emerging technology like speech recognition, there is lots of unknown territory. So when we executed usability testing for data collection last fall – with one thousand people in just eight weeks! – we had to make sure we provided enough guidance, but at the same time stay unobtrusive.
We also had to figure out how to motivate people quickly. Here are the most important things we learned.
When you’re curious about something new, there’s nothing better than consulting an expert.
We’ve posted in the past about the role of a QA tester in the localization process. To get even better insight, we’ve asked some friends to answer a few questions about the challenges and rewards of being a localization QA tester.
Since people seem to be eager to learn more about localization testing, we’ve decided to run a series to share our knowledge, based on the top 10 Google Suggest queries.
Want to learn more about localization testing? Read on!
If you’ve embarked on the process of localization testing, you might find yourself getting lost quickly. There are many steps to follow, and it’s important not to skip any if you want your project delivered on time and on budget.
To help you through it, we’re providing a handy checklist that will guide you through the process.