Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Hassle-Free Continuous Integration with Real Device Testing


Published on

Watch a live presentation at

Thousands of mobile apps are developed and released every day. The fierce competition for attention of end-users has changed the way mobile developers build and test their apps – and how they utilize today’s mobile devops tools to gain advantage of productivity, effectiveness and speed.

Stay tuned and join our upcoming webinars at

Published in: Technology
  • D0WNL0AD FULL ▶ ▶ ▶ ▶ ◀ ◀ ◀ ◀
    Are you sure you want to  Yes  No
    Your message goes here

Hassle-Free Continuous Integration with Real Device Testing

  1. 1. TheMobile DevOps Company Ville-VeikkoHelppi HeadofDemandGeneration/Bitbar Hassle-FreeContinuous Integration Combined with Real Device Testing WEBINAR NikitaAvvakumov Back-End Engineer/ GreenhouseCI
  2. 2. Presenters Agenda • The ‘Shift-Left’ Paradigm • Mobile DevOps & Agile • Delivery Pipeline for Mobile Apps • Absolute Requirements for Mobile DevOps • Hands-On Demonstrations o Build with Greenhouse o Test with Bitbar • Q&A Hassle-Free Continuous Integration Combined with Real Device Testing
  3. 3. The ‘Shift-Left’– WhatPeopleThinkIt Is Shift-Left Testing (happens earlier) Traditional Testing (happens before release)
  4. 4. The ‘Shift-Left’– WhatIt Actually Means
  6. 6. • Modern mobile app development is Agile, but development infrastructure does not support Agility well. • DevOps practices are emerging in to the intersection of Development, QA and Operations. • DevOps practice emphasizes the collaboration and communication of both software developers and operations while automating the process of software delivery and infrastructure changes. • DevOps practice establishes a culture and environment where building, testing, and releasing software, can happen rapidly, frequently, and more reliably. (Mobile) DevOps& Agile Development QA Operations Dev Ops
  7. 7. SPEED WINS It’s a simple fact. The faster you can deliver new applications, features and upgrades to market, and collect feedback, the better your business performs. For that you need higher development pace. And a lot of automation. THERE IS A DEMAND FOR MOBILE DEVOPS DevOps practices and tools have revolutionized the pace and quality of service delivery – but only for traditional server-based apps. FRAGMENTATION WITH TOOLS In mobile the delivery pipelines are more comple – in terms of tools and used methods. Cohesive and well-integrated development tool flow derives from Mobile DevOps practices. MANUAL DOING IS NOT EFFECTIVE Every stage requires a lot of manual work and silo’ed solutions from various vendors and/or open source tools. Why Mobile DevOps
  8. 8. DeliveryPipeline for Mobile Apps Development Source Code Management SCM Build Test Deploy Production Dev Tools: • IDEs • JIRA • Slack • etc. SCM: • Git/GitHub/ GitLab • Bitbucket • MSFT • etc. Continuous Integration and Build Automated Testing Automation for app store deployment, beta testers & enterprise app stores Production Monitoring and feedback to Dev
  9. 9. DeliveryPipeline withMobile DevOps Development Source Code Management SCM Build Test Deploy Production Dev Tools: • IDEs • JIRA • Slack • etc. SCM: • Git/GitHub/ GitLab • Bitbucket • MSFT • etc. Continuous Integration and Build Automated Testing Automation for app store deployment, beta testers & enterprise app stores Production Monitoring and feedback to Dev The Scope of Mobile DevOps
  10. 10. • Build and Continuous Integration must be tightly coupled when building mobile (Android and iOS) apps • Seamless integration ’backwards’ to SCM and ’forward’ with testing on real devices • Manual testing possible – but not recommended (due to efficiency of test automation) MobileDevOps: Build
  11. 11. ContinuousIntegration& Build CONTINUOUS INTEGRATION
  12. 12. • Use of real mobile devices • Fully automated from Build to Test (critical) via API • Debugging, problem fixing using various test results (logs, videos, screenshots) • Use of test automation MobileDevOps: Test
  13. 13. WhyMobile App Tests Fail?
  14. 14. The US & Global Coverage US Market 45 Android devices =~ 2 / 3 market Global Market 75 Android devices =~ 1 / 4 market ~90% market coverage can be achieved with 140 devices ~50% market coverage can be achieved with 175 devices
  15. 15. Local vs. Cloud-based Testing
  16. 16. • Must be fully integrated with and preferably online tool to automate tedious process of deploying new release for its targets • Automation cuts the work effort of days to hours • Must be seamlessly integrated with testing (test automation) MobileDevOps: Deploy
  17. 17. • Monitoring mobile apps on real networks, using real devices and real back-end connection • Synthetic monitoring vs. RUM • Must be seamlessly integrated with testing (and can utilize various testing practices, frameworks, scripts, etc.) MobileDevOps: Monitoring
  18. 18. MobileDevOps - User Experience Development/ IDE SCM Build Automated Testing Deploy / Release “Production” Automated builds for every code change Built binaries automatically tested Tested applications, Screenshots for various devices and languages, certificates, metadata ready to push to App stores Deploy To Devices Test apps in real world (Synthetic) Apps Used by Users • Synthetic Monitoring • Real User Monitoring Beta Testing (Humans)
  19. 19. TestOn Real Devices Automation- Quickly andEfficiently UseExisting AssetsNowand Future Tools PlatformDesignedForAgile Development • Test real world scenarios on real, non-emulated devices with 100% certainty • See exactly what the user experiences • Reduce time and headache of device acquisition and management The Key Things to Boost Mobile DevOps • Use any automation framework or test exercisers (e.g. Testdroid App Crawler) to get instant reports and results • Hit the ground running and get actionable results on a wide range of devices • Run more tests across more devices in less time, with fewer resources • Bring your own hardware, tools and frameworks and the Bitbar team will integrate them into the cloud • Bitbar solutions will not lock you in to any tool or automation framework • No vendor lock-in means that you have a long term and future proof platform for all of your mobile development and testing needs • Bitbar integrates seamlessly to your development tools and CI process • Instant results give immediate feedback to the development team • Faster iterations mean more efficient development, faster time to market and more satisfied users
  20. 20. • Standard hardware • Highly scalable environments • Plug-and-Play of new devices • Android & iOS • Extremely cost effective Infrastructure
  21. 21. Public Cloud On-Premise • Device ‘Cloud’ built for internal testing use • Enterprise-grade testing infrastructure hosted by the customer • Usually sits behind customer firewall and connects to preproduction environments • Private Device Cloud • Reserved and Dedicated devices • Hosted and Fully Managed by Bitbar • Devices chosen by and reserved exclusively for customer • Also known as Testdroid Cloud • On-demand devices (multi-tenant) • Mobile App testing on over 1000+ real Android and iOS devices hosted by Bitbar Private Cloud Bitbar Testing Deployment Options
  22. 22. Demo
  23. 23. THANK YOU! Moreinformationabout mobileapp testing, mobilemonitoringand mobiledevopsat