Globalization Testing - with an Emphasis on Translatability Testing and Pseudo Translation
Instructor: Dale Schultz09:00 - 17:00 : Monday, June 23, 2008
Workshop Agenda
| 09:00 - 09:15 |
Welcome and Introduction |
| 09:15 - 10:15 |
Globalization Testing |
| |
- Why is globalization testing needed?
- What is, and what is not, adequate globalization testing?
- Why is simply repeating tests in different locales not good enough?
- When should globalization testing be done?
- How does one determine what is needed for adequate testing?
- What teams in the organization are best positioned to do globalization testing?
- How do teams find out how to test and what test data to use?
- What tools are useful in globalization testing?
- What organizational structures and techniques are efficient?
Questions and answers on Globalization Testing |
| 10:15 - 10:45 |
Coffee Break |
| 10:45 - 12:15 |
Translatability testing |
| |
- What is translatability testing?
- Why is it so important?
|
| |
Pseudo Translation - a translatability test tool |
| |
- Who should generate the pseudo translation?
- Who should perform the testing?
- What to include in a pseudo translation
- How much expansion should there be?
- Types of translatability problems that can be found through pseudo translation testing.
Questions and answers on Pseudo Translation |
| 12:15 - 13:30 |
Lunch |
| 13:30 - 14:30 |
Practical application of Pseudo translation |
| |
Now that you have a pseudo translation of your software - what should the test team do? Switching to the pseudo translation
- Looking for language switching failures
- Looking for installation failures
Testing pseudo translated screens
- Looking for hard coded resources
- Looking for text corruption
- Looking for layout and truncation problems
- Looking for concatenation problems
- Looking for functional breakage
- Looking for incorrect audience designations
Ignoring strings from library code
Pseudo Translation and Bidi
Questions and answers on Pseudo Translation testing
|
| 14:30 - 15:00 |
Coffee Break |
| 15:00 - 16:00 |
Exercises - recognizing translatability issues |
| |
Practice identifying translatability defects |
| |
Open discussion on experiences, potential problems, cost savings, etc. |