Scope of Automation For Globalization Testing. By Bhaskar Mittapalli Yateesh Kumar Shukla

Transcription

1 Scope of Automation For Globalization Testing By Bhaskar Mittapalli Yateesh Kumar Shukla

2 Agenda Introduction 2 Challenges in Testing Globalized Applications 3 Guidelines for Globalization Testing 4 Leveraging Automation 5 Comparative study 7 Benefits of this approach 9 Conclusion 10 1

3 Introduction What is Globalization? Globalization is the process of making the software application ready to the end users where it supports multiple languages and culture specific settings without sacrificing any of the functionality and core logic. Need for Globalization Reach out to the global customers by providing language specific interfaces To support region specific requirements (due to legal, financial practice) To improve the effectiveness of a globally distributed business 2 k

4 Challenges in testing globalized applications Language specialists are required to test translated content Tests should be performed across different locales Challenges of testing global applications Tests should include validations for the display of date formats, currency masks etc. and is time consuming More effort required to author test scenarios for various locale specific scenarios 3 k

5 Guidelines for Globalization Testing Develop a comprehensive test plan Identify areas where locale awareness is required Use varied combination of inputs Provide time for pseudo-localization Perform extensive GUI testing for high priority test cases Leverage automation for checking translated content and business rules specific to different locales 4

6 Our Approach: Leveraging Automation Identify the automation scenarios Check availability of locale specific data Identify the locales under test Prepare the navigation flow Run the test for specific locale 5

7 Our Approach: Leveraging Automation CHECK LOCALE SPECIFIC DATA CHANGE THE LOCALE AUTOMATION TOOL READ USER LOCALE RUN SCRIPT FOR SPECIFIC LOCALE 6

8 ROI Comparing Test Case Authoring Efforts Total Hours: Without Automation: 360 min With Automation: 285 min Without Automation With Automation Microsoft Office el Worksh 7 Automation Scripting Efforts

9 ROI Comparing Test Case Execution Efforts Total Hours: Without Automation: 240 min With Automation: 120 min Without Automation 8 With Automation Microsoft Office el Worksh 8 Automation Execution Efforts

10 Benefits Time savings in test authoring efforts for different translated versions of the application. Test execution time is saved when the automated scripts are run on different locales and languages. Language specialists are needed to a lesser extent for the testing of the applications. Exhaustive language specific UI testing is easier. 9

11 Conclusion By using the above generic automation framework, validations can be done for the static text as well as some of the key business rules of the application. This approach would be suitable for applications which have more numerical data and static text changing over locales. Example: Banking Applications. We strongly believe that the strategies identified will save time and thus more time could be spent on other priority tasks and thus provide better quality assurance. 10

12 Questions?

13 About Deloitte Deloitte refers to one or more of Deloitte Touche Tohmatsu, a Swiss Verein, and its network of member firms, each of which is a legally separate and independent entity. Please see for a detailed description of the legal structure of Deloitte Touche Tohmatsu and its member firms. Please see for a detailed description of the legal structure of Deloitte LLP and its subsidiaries. Member of Deloitte Touche Tohmatsu