Translation Verification Testing

1. Translation Verification Testing Rational Insight - Jiang Xuan 2012-08-02

2. Globalization Testing - Agenda • What does translation testing do? • General process of translation and testing • Why is translation testing important? • GVT v.s. TVT • Translation testing in DEV lifecycle • Organizational structures

3. What does translation testing do? • Translation testing is to test Translation Quality, not Functionality • Translation testing is to • verify translation quality after translated files are built into product • check missing translation • ensure the translated files use correct codepage • double check if mnemonic key is probably assigned

4. What is translation testing NOT to do? • Translation testing is NOT to • test product functions in different language environment(product function should work the same in different language environment) • test I/O of national characters(it’s scope of globalization testing, not translation testing) • verify whether translation is not corrupted by build process(it’s scope of globalization testing by using pseudo translation, not translation testing) • ensure culture data format can be displayed correctly(it’s scope of globalization testing, not translation testing)

5. General process of software translation

6. Project Management & Test Coordination Product Study/Training Preparation Test Plan Development Test Plan Review Test Cases Development Test Environment Setup Test Cases Review Defects Resolution Pre-Test Execution Conference Calls for Status Review & Defects Discussion Execution Test Execution/Support Test Go/No-Go Decision Test Exit Memo Translation Signoff Closing Lesson-Learned General process of translation testing

7. What does translation testing focus on

8. Why is translation testing important? • Translation testing is to ensure the product translation quality, which can • expand worldwide business opportunity • improve product usability for non-English speaking users • raise customer satisfaction • To detect and fix problems of translated files • missing translation • wrong codepage • layout adjustment • Mnemonic key arrangement

9. What are the differences between globalization testing and translation testing? • Globalization testing focuses on code and English source files • Translation testing focuses on translation quality and translated files • There are some common symptoms, like English strings, corruption, but root causes are different • Normally while globalization testing is executed, real translation is not available yet, and those problems don’t happen with pseudo translation

10. When is the best timing to do translation testing? • Functional testing is completed • Globalization testing is completed • at least Translatability part • Translation is completed and integrated into a build • Translated files are integrated into build • System testing is at least 65% completed

11. Where is translation testing in development cycle? Concept Phase Plan Phase Development & Quality Phase Design Coding & Unit Test Functional Testing System Testing Globalization Planning Globalization Testing Translation Planning Translation Translation Testing

12. What organizational structures are efficient? Translation Center(s) Test Support Product Development Translation Center Planner Test Support TeamProject Manager Globalization Project Manager Translation Test Lead Product Development Support Engineer/ File Handler Translation Tester PM Communication Technical Discussion

13. www.ibm/software/rational

14. Revision History