Enabling devOps to Achieve Continuous Testing and Release Monitoring to Accelerate Mobile apps

The current situation reflects the organisational desire to ship faster with adherence to highest level of product quality. Testing should be carried out at every level of product development so that we achieve the highest quality level with minimised risk and cost post the software development cycle. With implementation of Continuous Integration enabling various quality gates ensure right code make its way to main-line.

Continuous Delivery enables teams produce software in short cycles, ensuring that the software can be reliably released at any time and, when releasing the software, doing so manually. Building an infrastructure that helps in taking decision on decision on increment rollout and halts asks for integrating automated analysis of various metrics (Crash monitoring , Playstore feedback sentiment analysis, current performance of app on market and other key User engagement metrics) to post release tracking of mobile apps.

In this talk we will share some experience on how the above can help in shipping faster with more quality and at the same time enabling Devops automate build release process and App Performance monitoring.

 
2 favorite thumb_down thumb_up 2 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/Structure of the Talk

  • Enabling various Quality Gates on Mobile Continuous Integration
  • Integrating Integration Tests on CI and reduce test execution time by taking advantage of various Mobile Device Labs.
  • Path to Mobile Continuous Delivery.
  • Analysing Post release Metrics in order to take automated decision on phased rollouts and release halt.

Learning Outcome

  • Bringing Quality upstream in Mobile Application release cycle using CI
  • Enabling running GUI test on CI
  • Pre and Post release Performance monitoring

Target Audience

Managers , Leads , Directors , Release Engineers

schedule Submitted 7 months ago

Public Feedback

comment Suggest improvements to the Speaker
  • Pooja Shah
    By Pooja Shah  ~  5 months ago
    reply Reply

    Hi Vivek and Abhishek, 

    Thank you for the submission. This can definitely have good key takeaways. CI/CD is a challenge and sharing your insights would be a great add.

    However:

    • Does the scope of this lies in development practises and unit/functional test in the pipeline or it is beyond with End-End app tests run? (if "yes" then how about the time optimisation on test feedback)
    • Is it contextually on the lines of Appium? i.e. Do you plan to demonstrate the hurdles with appium tests while trying to set them in CI/CD? 
    • Any consumable open sourced tech/guidelines the attendees will leave with?
    • Where can we see it in action or read more about it?

     

    • Vivek Upreti
      By Vivek Upreti  ~  5 months ago
      reply Reply

      Hi Pooja

      The focuses on various strategies  (Monitoring app Crash Free Users , Performance , app sentiments) that can be adopted either in  pre or post releasing the app to market and how can we track them in order to take automated decision on halting the build on a certain rollout % or furthur releasing the app.We would be sharing some past experience on how we achieved this.

       

      • Does the scope of this lies in development practises and unit/functional test in the pipeline or it is beyond with End-End app tests run? (if "yes" then how about the time optimisation on test feedback)

       

      → This is beyond the unit/functional test and spans across end-end functional tests, non-functional (performance) tests that helps identify the key app performance indicators, to certains business related tests as well such as apk size. It is given that when you plug in more tests in your CI, time goes for a toss. We will also share the case study from our experience on how to tackle this by

      1. Leveraging the tools that helps us in reducing test execution time.
      2. Leveraging the containerisation (CI Tools) and test more in your CI system in less time
      • Is it contextually on the lines of Appium? i.e. Do you plan to demonstrate the hurdles with appium tests while trying to set them in CI/CD? 
        • We will be talking about this in a seperate talk submitted (Click here for the link)
      • We will be talking about both paid, open sourced tools that can be integrated into Delivery pipelines to track the application health.

  • Liked Vivek Upreti
    keyboard_arrow_down

    Vivek Upreti / Naresh Jain - Setting up Jenkins CI Pipeline using Appium tests for Android and iOS

    45 Mins
    Demonstration
    Beginner

    GUI and functional tests determine if the product is working correctly from an end user perspective. With increasing number of automated GUI tests we would want to automate when and where they are executed. Continuous Integration helps in merging code to a centralised repository frequently and find out issues early in development cycle in order to help push quality upstream.

    In the talk, you will see examples of how you can setup CI system for Android and IOS native/hybrid apps and how to plugin your Appium tests in the pipeline using Jenkins. We will also talk about the challenges we face while setting it up for Android and IOS applications. We will also talk about how to strengthen your CI pipeline via integrating various tests and Static code analysis tools.

    CI Pipeline