Transformational Automation Approach for Native Mobile Apps Testing of a Healthcare Application

1. Transformational Automation Approach For Native Mobile Apps Testing Of A Healthcare Application K A CHANDRAKANTH SENIOR MANAGER - SOFTWARE TESTING PRACTICE PricewaterhouseCoopers Service Delivery Center (Bangalore) India Private Limited

2. Abstract Mobile Application Testing especially for native applications and also for the web applications that can be accessed on mobile devices is fast gaining more wider attention than ever before. As the world gets smaller to reach, mobile revolution has taken the globe into its hand. More and more users rely on smaller hand held devices and use of desktops and laptops while being mobile has been drastically reduced. The paper highlights the facts on some unique methods adopted for a healthcare project which is related to development and testing of the client’s flagship mobile application through implementation of agile methodologies. The key differentiator in this entire program is that it had several projects within itself and each project had a unique method that was used for testing the native mobile app on different platforms including iOS and Android. Apart from the traditional testing methods, automation was extensively used which involved use of mobile devices hosted on cloud and also physical devices for functional testing purposes. Other forms of testing like accessibility testing was included to help users with different abilities to access the application on their mobile devices. Each of the project tracks used customized processes and metrics to implement the testing objectives and were able to successfully deliver the goods bringing client delight and exceeded the expectations

3. Client Challenges • Different Agile teams operating on different type of applications without utilizing best practices • Testing team in each of the Agile teams followed different methodologies and approach to deal with the application • Huge number of automation scripts to maintain. Manual Regression Testing • Unstable Test Environment on Live • Test Data request had to be raised to a third party vendor and had to wait till we receive the final test data prepared. Back and forth activities with the vendor to validate and get the test data corrected for discrepancies • Need to automate all the test cases in the same sprint rather than automating only the regression portion • Shorter sprint cycle of just 2 weeks to complete both Functional and Test Automation

4. Client Challenges • Different Agile teams operating on different type of applications without utilizing best practices • Testing team in each of the Agile teams followed different methodologies and approach to deal with the application • Huge number of automation scripts to maintain. Manual Regression Testing • Unstable Test Environment on Live • Test Data request had to be raised to a third party vendor and had to wait till we receive the final test data prepared. Back and forth activities with the vendor to validate and get the test data corrected for discrepancies • Need to automate all the test cases in the same sprint rather than automating only the regression portion • Shorter sprint cycle of just 2 weeks to complete both Functional and Test Automation

5. Application Setup Flagship Mobile Native Application Agile Team 1 Agile Team 2 Agile Team 3 Agile Team 4 App 1 App 3 App 2 App 4 PROJECT 1 PROJECT 2 PROJECT 3 PROJECT 4 Android and iOS

6. Approach – 1 – Integration • Automation scripts were developed in Selenium and Appium using Perfecto mobile cloud devices. • API integration and team site validation to validate jsonresponse(from the server). • Automating the responsive web design in different OS versions for both the platforms. • Continuous integration is integrated with Jenkins job for executing the regression runs. • Test execution was completed in two phases. First phase scripts will be a single base code for Android and iOS platforms with various OS and device screen size. Second phase confirmed that the scripts will be executing on all the platforms and environments including virtual service. • The testing we conducted was in larger volume compared to what would be considered as real time experience.

7. Approach – 2 - Transformation Transformation • Identify set of test cases that can be covered at • API LAYER • APP LAYER • UI LAYER • Minimal End to End UI scenarios for complete flow of user story Transformation Optimized UI Testing Moderate App Logic Testing Increased API Testing

8. Approach – 3 - Simulation Challenges: • Limited device availability to cover huge volume of test scripts POC: • Identify test cases that are with functional flow • Verification not depend on device specific • Pick up one module • Configure the existing framework to work with simulator • Verify/execute identified test cases on simulator and compare the results with execution on real devices • Setup the virtual machine for Simulator and configure with build management system Outcome: • Have complete scripting, execution on build management system and result generated – Complete flow • Results should be the same in terms of verification • Reduction in terms of execution time • Reduction in terms of device related failure

9. Benefits and Advantages • More focus on increased testing on ‘Major’ devices only • Low Maintenance of automation scripts • Test jobs would run on stable setup • Multiple testers can access the system at the same time • Increased pass percentage of automated tests • Successful automation of complex modules and test scenarios including non functional scripts • Elimination of the manual efforts for regression runs • Scripts can be executed on all versions with different OS configuration including localization for both platforms (Android and iOS)

10. References & Appendix • Mobile Application Testing • http://www.softwaretestingclass.com/introduction-to-mobile-application-testing/ • Mobile Testing Process • http://www.rapidvaluesolutions.com/mobile-application-testing-step-by-step-approach/ • Mobile Apps Testing Types • https://en.wikipedia.org/wiki/Mobile_application_testing • Mobile Testing in the Cloud • http://www.softwaretestinghelp.com/beginners-guide-to-mobile-application-testing/

11. Author Biography • K A Chandrakanth is a hands on Techno-Senior Manager with PwC SDC Bangalore. He has wide exposure to product testing, services testing and IT consulting experience. He has around 17 years of core testing skillset and has extensively worked on functional testing, test automation, performance testing, security testing and web services testing areas. He has excelled in test management activities and has played multi dimensional roles in project management, program management, software testing, quality consulting and quality assurance. He has contributed in setting up large Testing Center of Excellence groups to focus on Kaizen initiatives and has worked for key global clients in defining the strategy and approach for managing complex applications. He has wide knowledge on testing methodologies including Agile and has played a variety of roles like product owner. scrum master etc.. for leading global clients. He has authored several papers and regularly participates in global testing conferences. He is a certified scrum master and also has completed his certification in scaled agile framework (SAFe 4.0). He has played client facing role and managed the transformation of large legacy programs into the newer technological advances through effective implementation of cutting edge technologies

12. Thank You!!!