Infostretch is a leading provider of mobile application lifecycle services founded in 2004, offering continuous integration (CI) practices that allow for immediate testing of code changes. The document outlines CI's key principles, including source control, automated builds, and self-testing, which enhance software quality and reduce operational overhead. A case study exemplifies optimizing CI within a healthcare provider's mobile application testing processes, significantly reducing test execution time and improving efficiency.

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 is CI?
 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 InfoStretch Corporation.
 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
 Shell scripts
 Tools: Maven, Gradle, Ant, Spring IO, ChaiOne, Xcodebuild
8©2015 InfoStretch Corporation.

9. CI Build Tool
9©2015 InfoStretch 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
 Deploy Mobile 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
Code quality 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 Clone to 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) You do 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©2015 InfoStretch 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 InfoStretch Corporation.
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 with InfoStretch
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, Mobile Labs
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-DEMAND CLOUD AUTOMATION
SUPPORT
INTEGRATION WITH
SUPPORT SYSTEMS
What does it offer?

23. 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

24. 25©2015 InfoStretch Corporation.

25. ©2015 InfoStretch Corporation. All rights reserved. 26
Thank You
info@infostretch.com
www.infostretch.com