IBM 国际化测试介绍 (GlobalizationTesting).ppt

* What organizational structures and techniques are efficient? Small set of globalization experts Provide guidance to non globalization expert testers Help determine what to test Provide test data and test steps Ensure setup documentation is in place Review test plans for globalization coverage Act as ‘go to’ people when questions come up At design phase For development For testers For management Development Ensure that pseudo translation generator is in place * Benefits Reduced costs of fixing defects by finding them earlier in the development process Lower translation costs Better consumability worldwide - Increased customer satisfaction * Globalization testing - Summary Enabling Translatability Not translation or localization * Questions? Thank you! * * Dale Schultz dale_schultz@ * Very generic software development cycle * * There are two main parts of Globalization testing: Global enablement and translatability * Globalization test is just one of many tests performed within IBM and can be regarded as a subset of functional testing. * Globalization testing is looking for specific functionality, it is not simply repeating functional tests in different locales * Using the English version or user interface, user get culturally appropriate support such as mirrored calendar, alternate calendar systems etc. * The window title should also say Testing Double Byte Character * Repeating tests for a set of locales (even a carefully selected set) and platforms is not efficient. Testing all locales is impossible. What is needed is specific tests that test specific functionality that is evident and required in specific cultural envionments. * Treat Globalization testing as a subset of normal functional testing. It is after all inherent functionality, so it makes sense to do it at the same time as the rest of the functional testing. * Corporate expertise was concentrated into a solution that enabled people across the company to determine what to test and how to do i