Download to read offline
![Case Study: CI implementation for Leading Healthcare Provider Customer Challenges Slow automation execution Time- 22 mins per test case Sequential module wise execution on one device @ a time Already automated script not utilizing in regression cycles Lots of test data dependencies and require regular maintenance No framework available for Responsive web design for mobile InfoStretch Approach Recommended best practices for automating native & web app using perfecto cloud Collaborated with Scrum Team and understand web- service/JSON role in test data generation/creation Setup continuous integration for nightly execution for utilizing cloud devices on free time Proposed HP ALM integration along with Jenkins for complete automation life cycle Engagement Benefits Optimize automation execution to 8-10 mins per test cases [Reduce 50%] Enabling parallel execution on all perfecto cradle Utilizing automation script in regular code drop/release cycle [2-3 times per week- average 1200 test cases executed in each cycle] Develop framework utilizing JSON response instead of test data in xls sheet on run time. [Almost 0% test data dependency and maintenance] Created new framework which supports common code for execution on desktop and mobile browsers on perfecto devices for Response Web design](https://image.slidesharecdn.com/cifinaljunewebinar-150826221102-lva1-app6891/75/Continuous-Integration-for-Mobile-App-Testing-23-2048.jpg)
Uploaded byMartin Smith
Continuous Integration for Mobile App Testing
Infostretch Corporation, established in 2004, specializes in mobile application lifecycle services and emphasizes the importance of continuous integration (CI) for enhancing software development practices. CI allows for immediate testing and reporting of code changes, improving project visibility and quality assurance through automation and streamlined processes. The document also outlines CI implementation techniques, tools, and a case study demonstrating the optimization of automated testing for a healthcare provider.
Continuous Integration for Mobile App Testing
- 1. ©2015 InfoStretch Corporation June,2015 US - UK - India Continuous Integration for Mobile App Testing Harnessing the power of ultimate Mobile automation using - CI and Cloud
- 2. Apps Tested Employees 100+ Apps developed and deployed 3000+ Global Footprint Locations Corporate HQ: Silicon Valley Offices: Conshohocken (PA), Ahmedabad (India), Pune (India), London (UK) 700+ 250K Active Mobile Customer Engagements 60+ About Infostretch Real devices in mobile labsAbout us Founded in 2004 in Santa Clara, CA, InfoStretch is a leading provider of next- generation mobile application lifecycle services ranging from design and development to testing and sustenance. 2©2015 InfoStretch Corporation.
- 3. Agenda What isCI? Why CI and Value to Business CI Implementation and Architecture Mobile Cloud Solutions & CI Case Study 3©2015 InfoStretch Corporation.
- 4. What is CI? Continuous Integration is a software practice in which isolated code changes are immediately tested and reported on as soon as they are added to the code base. Key Principles of CI include: Implement Source Control system Automate the Build Process Frequent Commits, Code Consolidation, Fast builds Automated Deployment Self testing the builds: Unit tests, Code Quality, Static Analysis Testing in a Clone to Production environment Automate User Acceptance Test Dashboards for Reporting 4©2015 InfoStretch Corporation.
- 5. What is CI? Continuous Integration is a software practice in which isolated code changes are immediately tested and reported on as soon as they are added to the code base. Key Principles of CI include: Implement Source Control system Automate the Build Process Frequent Commits, Code Consolidation, Fast builds Automated Deployment Self testing the builds: Unit tests, Code Quality, Static Analysis Testing in a Clone to Production environment Automate User Acceptance Test Dashboards for Reporting 5©2015 InfoStretch Corporation.
- 6. Source Control 6©2015 InfoStretchCorporation. Git Decentralized, and aims to be fast, flexible, and robust Subversion Open source version control system inspired by CVS CVS Built on RCS, with emphasis put on security and source code correctness Vesta Build system with a versioning file system and support for distributed repositories
- 7. What is CI? Continuous Integration is a software practice in which isolated code changes are immediately tested and reported on as soon as they are added to the code base. Key Principles of CI include: Implement Source Control system Automate the Build Process Frequent Commits, Code Consolidation, Fast builds Automated Deployment Self testing the builds: Unit tests, Code Quality, Static Analysis Testing in a Clone to Production environment Automate User Acceptance Test Dashboards for Reporting 7©2015 InfoStretch Corporation.
- 8. Build Automation Shellscripts Tools: Maven, Gradle, Ant, Spring IO, ChaiOne, Xcodebuild 8©2015 InfoStretch Corporation.
- 9. CI Build Tool 9©2015InfoStretch Corporation. Jenkins / (fka Hudson) Open source continuous integration tool written in Java CruiseControl Open source continuous integration tool written for Java-based frameworks Bamboo Bamboo is a continuous integration server from Atlassian TeamCity Continuous integration and build management
- 10. What is CI? Continuous Integration is a software practice in which isolated code changes are immediately tested and reported on as soon as they are added to the code base. Key Principles of CI include: Implement Source Control system Automate the Build Process Frequent Commits, Code Consolidation, Fast builds Automated Deployment Self testing the builds: Unit tests, Code Quality, Static Analysis Testing in a Clone to Production environment Automate User Acceptance Test Dashboards for Reporting 10©2015 InfoStretch Corporation.
- 11. Automate Deployment DeployMobile apps to Physical devices/ emulators using deployment tools Tools: Testflight, Hockey App, IBM Urban Code, etc 11©2015 InfoStretch Corporation.
- 12. What is CI? Continuous Integration is a software practice in which isolated code changes are immediately tested and reported on as soon as they are added to the code base. Key Principles of CI include: Implement Source Control system Automate the Build Process Frequent Commits, Code Consolidation, Fast builds Automated Deployment Self testing the builds: Unit tests, Code Quality, Static Analysis Testing in a Clone to Production environment Automate User Acceptance Test Dashboards for Reporting 12©2015 InfoStretch Corporation.
- 13. Self Testing Builds Codequality tools like: SonarQube and Static Analysis tools like: Fortify 13©2015 InfoStretch Corporation. Junit A popular framework for writing unit tests in Java/J2EE environment TestNG Similar to jUnit, but provides dependencies and expanded annotations Nunit includes GUI, command line, integrates into Visual Studio MSTest A command-line tool for executing Visual Studio created unit tests outside of the Visual Studio IDE Not really a testing framework as it is a part of the Visual Studio Unit Testing Framework Rspec Behaviour-driven development framework
- 14. What is CI? Continuous Integration is a software practice in which isolated code changes are immediately tested and reported on as soon as they are added to the code base. Key Principles of CI include: Implement Source Control system Automate the Build Process Frequent Commits, Code Consolidation, Fast builds Automated Deployment Self testing the builds: Unit tests, Code Quality, Static Analysis Testing in a Clone to Production environment Automate User Acceptance Test Dashboards for Reporting 14©2015 InfoStretch Corporation.
- 15. Testing in Cloneto Production Load/Performance testing using tools like Soasta 15©2015 InfoStretch Corporation. CI Servers typically control CD activities now as well Server Scripts are written to push new releases into downstream environments These scripts can be launched manually with a “button push” or tied together into an automated delivery pipeline that moves new versions of applications through environments automatically as tests are passed Without effective testing, Continuous Delivery (and also DevOps in general) cannot be optimized! Bad automated tests used to result in bad test results faster Not bad automated tests result in bad code being deployed! IT Automation Tools allow teams to define environment, system, and application configurations and parameters such that downstream environments can be automatically provisions and any conflicts between expected application parameters can be identified Significantly reduces the amount of operational IT support needed for environment setup, application installation/configuration, and teardown necessary to move applications from development to production 80-90% decrease in ops support with accelerated delivery Common Tools: Puppet, Chef, Ansible IT Automation Tools
- 16. Why CI? 6) Youdo not have automated builds or automated tests in place. 16 1) Mobile apps live and die by their ratings in an App Store 2) You are "going commando" without source code management for your mobile app deployment process. No tracking. No rollback. 3) You are deploying manually between environments 5) You are stuck in a "hot mess" of hotfixes 4) You are editing configurations manually, doing it on staging or production environments ©2015 InfoStretch Corporation.
- 17. Value to Business 17©2015InfoStretch Corporation. Key Benefits of Continuous Integration Early defect detection Measurable health of software Brings quality assurance Reduce overheads Better project visibility Reduce assumptions
- 18. CI/CD Process 18©2015 InfoStretchCorporation. DELIVERY TEAM VERSION CONTROL BUILD & UNIT TESTS AUTOMATED ACCEPTANCE TESTS USER ACCEPTANCE TESTS RELEASE check in trigger feedback check in trigger feedback trigger feedback check in trigger trigger approval approvalfeedback feedback START
- 19. CI Jumpstart withInfoStretch 19 REVIEW 1 to 2 weeks Understand the expectation from the different stakeholders Understand branching strategy Qualification of the builds product and maintenance release cycle Understand dependency managements Understand the release engineering policies DEFINE 4 to 6 weeks Development & release build environments Multi-site development coordination – broken builds resolutions Release engineering and CI flow design Define branching and merging strategy Define CI test automation execution DEPLOY 2 to 4 weeks CI Tools selection Design trunk, branching and merging strategy to support product development Design step by step CI flow and scripts needed Automate software builds and packaging deployment scripts Validate starting, executing and report of basic build test verification 1| ©2015 InfoStretch Corporation. 2| 3|
- 20. SYNCHRO,Perfecto, Sauce Labs, MobileLabs CI/CD Architecture Using Mobile Cloud 20©2015 InfoStretch Corporation. GitHub/SVN /TFS Jenkins/H udson/Tea mCity/Circ leCI Developers Data Center CI Machines iOS/Android devices Dashboard Functional, Non-Functional, Regression, Smoke Tests… iOS/Android simulators
- 21. CI tools &Mobile Cloud Integration 21©2015 InfoStretch Corporation. Benefits of harnessing - CI and Cloud: Flexible and Mobile-ready Plugins Unlimited Scalability and Device Elasticity Leverage Existing Processes and Assets Within An Organization Enhance Mobile CI Workflow in Real User Conditions On-demand Availability Faster Issue Resolution
- 22. Mobile QA Solutions ON-DEMANDCLOUD AUTOMATION SUPPORT INTEGRATION WITH SUPPORT SYSTEMS What does it offer?
- 23. Case Study: CIimplementation for Leading Healthcare Provider Customer Challenges Slow automation execution Time- 22 mins per test case Sequential module wise execution on one device @ a time Already automated script not utilizing in regression cycles Lots of test data dependencies and require regular maintenance No framework available for Responsive web design for mobile InfoStretch Approach Recommended best practices for automating native & web app using perfecto cloud Collaborated with Scrum Team and understand web- service/JSON role in test data generation/creation Setup continuous integration for nightly execution for utilizing cloud devices on free time Proposed HP ALM integration along with Jenkins for complete automation life cycle Engagement Benefits Optimize automation execution to 8-10 mins per test cases [Reduce 50%] Enabling parallel execution on all perfecto cradle Utilizing automation script in regular code drop/release cycle [2-3 times per week- average 1200 test cases executed in each cycle] Develop framework utilizing JSON response instead of test data in xls sheet on run time. [Almost 0% test data dependency and maintenance] Created new framework which supports common code for execution on desktop and mobile browsers on perfecto devices for Response Web design
- 24.
- 25. ©2015 InfoStretch Corporation.All rights reserved. 26 Thank You info@infostretch.com www.infostretch.com
Editor's Notes
- #7 Page 24 from PDF document.
- #9 Alicia can you put relevant logos for each of the tools.
- #10 Page 27 from PDF document.
- #12 Alicia can you put relevant logos for each of the tools.
- #14 Page 35 of PDF and logo for SonarQube and Fortify
- #16 Page 46-47 of PDF
- #17 ) You are stuck in a "hot mess" of hotfixes. Not uncovering problems early. Forced into making changes late in the game. You are deploying manually between environments. It's slow. It's brittle. It's painful. You hear the all too common "it works on my device" uttered by your developers. Then it breaks on staging and production.
- #18 Defects are detected and fixed sooner – Integrating testing throughout the development process would give QA teams more time to find bugs and help prevent bugs from effecting later code. Health of software is measurable – By establishing continuous testing into the automated integration process, the software health attributes such as complexity can be tracked over time. Reduce assumptions – Continuous Integration gives the chance to replace assumptions with knowledge thereby eliminating all cross-platform errors at the development stage. Reduce overheads – Finding a bug at the development stage is the cheapest possible way to find it. If the same bug was to be fixed in any other environment, it would cost more. Setting up a CI system may cost an overhead, but will outweigh the man-hours saved along the way. Brings quality assurance – This is the biggest benefit from a client perspective, continuous integration can enable you to release deployable software at any point in time. In the absence of CI, projects are prone to delayed releases because of unforeseen issues which arise from deployment. Enables better project visibility – Since integration occur frequently, it provides the opportunity to notice trends and make informed decisions. Noticing trends in build success or failure, overall quality becomes possible. With CI, you can access real-time data on the code quality metrics to innovate new improvements and support decisions. It also offers the ability to generate API-like documentation for all committed code, making the software architecture immediately visible to new developers and other team membersIn terms of software quality, CI can help you measure cyclomatic complexity, code duplication, dependencies and coding standards so that developers can proactively refactor code before a defect is introduced. If a defect is introduced into a code base, CI can provide feedback soon after, when defects are less complex and less expensive to fix. Also, when using an effective developer testing regimen, CI provides quick feedback, via regression tests, on software that was previously working and is adversely affected by a new change. How about ROI? Calculate how much time your team spends on fixing defects once the software is with the testing team -- QA, integration testing, etc. Of course, it costs considerably more once it enters production. When implementing effective CI practices, you can discover many of these defects as soon as they are introduced, which significantly decreases the cost of fixing each defect. CI is really important to moving fast, or just to move with the confidence you are not breaking anything CI provides benefits like : Rapid feedback on the "health" of the software under development Identification of defects early on in the development cycle Significant reduction to the cost of fixing each defect
- #19 CHANGED BUILD & UNIT TESTS, need to add deployment in here.
- #22 A Flexible and Mobile-ready Plugin – Support your most complex use cases by automatically deploying mobile apps, executing your test code, and assuring high quality delivery of any mobile app style. Unlimited Scalability and Device Elasticity for Your Entire Release Cycle – Ramp up from single device testing to full, cross-platform load testing on hundreds of devices worldwide. Enterprise-ready and Continuous Quality - Our SLA based cloud and local deployment services are consistent, stable and secure, which is great for global, distributed team collaboration. Leverage Existing Processes and Assets Within Your Organization - Connect your existing mobile app development tools to the Jenkins plugin in order to execute your test code against your "hybrid" MobileCloud lab of real devices. Enhance Mobile CI Workflow in Real User Conditions - Test on real devices, in real-time with real network conditions across different geographies. On-demand Availability – Execute tests anytime, from anywhere with continuous access to a cloud-based test bed of active, carrier connected mobile devices Faster Issue Resolution – Foster agility with rich reports that include screenshots and videos to clearly demonstrate what went wrong and where
- #23 Cloud Distributed Team Access Cost Efficient Team Engagement Sharing / Test Execution Proofs Automation What type of tools / language support Selenium / UFT Support Integrations Test Management System / CI Integration
- #24 Note: Removed Roles and skillsets from slide title because it is repeated as slide bullet headers.
- #27 Social media icons would be good for presentations done for outside of InfoStretch audiences.