What was your strategy for iOS 10 testing?

Every year apple comes with a new version of iOS and new apple devices. As a mobile testers I hope you must have come across this situation recently. What was your strategy and how did you test the new iOS 10 Upgrade in your company? 

You need to be a member of Mobile QA Zone to add comments!

Join Mobile QA Zone

Email me when people reply –

Replies

  • It’s true every year apple comes with a new version of iOS and new apple devices and it becomes very difficult to keep watching of the health status of the existing iOS application in new environment provided by new version of iOS and hardware.

     

    We are keeping watch on compatibility of new features of iOS 10 with the existing application e.g.  Below are the new features of iOS 10 to check the compatibility further:

     

                  -Swipe-up-from-the-bottom menus is now split into several panels

                  -Broken into: quick settings, media playback and Apple Home

                  -Touch detection issues for brightness slider vs sliding between panels

                  -iOS 10 automatically pieces together photo albums for you

     

    In a changing environment I prefer to perform "User testing" to evaluate an apps without a bug e.g. concept testing, usability testing, beta testing and A/B testing.

     

    In our testing of iOS app our QA engineer's prime objective is to check the functionalities of the software system. We mainly concentrates on below points while QA an iOS app -

     

    -          Mainline functions:  Testing the main functions of an application

    -          Basic Usability: It involves basic usability testing of the system. It checks whether an user can freely navigate through the screens without any difficulties. In iOS testing, usability test could be recorded to remember or to share with others.

    -          Accessibility:  Checks the accessibility of the system for the user

    -          Error Conditions: Usage of testing techniques to check for error conditions.  It checks whether suitable error messages are displayed.

     

    Further, we are following below procedures:

    -          Improve one's testing methods gradually.

    -          Very important is to document application bugs using built-in screen short command. It helps QA engineer to understand how the bugs occur in changing environment.

    -          Crash reporting is useful tools when test your application. They can detect crashes and log detail so you can investigate the bugs easily in new iOS environment.

    • Thanks for inputs. After some brainstorming, we created some strategy for testing iOS upgrades. As we work in enterprise, our testing strategy takes care of upgrades in iOS as well as upgrades in enterprise Mobility management solution.

      How we decided to go about at least for iOS Upgrade/Update is:

      3040209364?profile=original

      We do kind of impact analysis for each new iOS upgrade. see below. This is impact analysis for iOS 10.2 PUBLIC beta 2.

      3040209431?profile=original

      Based on impact analysis we check how much testing effort is required.

This reply was deleted.
    results->result as $result) { ?>
  1. jobtitle;?>
    company;?>(formattedRelativeTime;?>)city;?>, state;?>
    Welcome to Mobile QA Zone, a Next Generation Software Testing Community.Invite your friends to join this community.Write to us to become a featured member.