Downloaded 12 times
Uploaded byPerfecto by Perforce
Are you Ready to Test on iOS 9?
The document outlines a webinar presentation by Eran Kinsbruner on iOS 9, emphasizing key features and enhancements that impact development and testing, including Apple Pay, improved map functionalities, and new platform requirements like IPv6. It highlights the implications for test code maintenance, platform robustness, and the need for new test cases, specifically for the iPhone 6s and other devices. Additionally, it discusses the importance of optimizing testing environments and continuous testing for successful app deployment.
More Related Content
Similar to Are you Ready to Test on iOS 9?
Are you Ready to Test on iOS 9?
- 1. Are you readyto test on iOS9? Eran Kinsbruner Dir, Product Marketing Mobile Technical Evangelist Perfecto Mobile A Perfecto Mobile Webinar September 2015
- 2. Some Housekeeping beforewe start Submit questions using the Q&A panel. Participate in the polls Watch your email for a copy of the recording and slides Complete the survey following the presentation
- 3. Agenda • iOS9 KeyFeatures Introduction • iOS9 Enhancements - Dev/Test Implications • Live demo • Q & A 3
- 4. Expect Fast iOS9 Adoption 4 Source: Mixpanel
- 5. Poll 1 –What were the main challenges in the previous iOS release? • Performance degradation • Functional defects • Real device testing accessibility • Test plan refresh • Don’t know
- 6. Key iOS9 OSEnhancements – Available 9/16 • Apple Pay • Apple Car • Productivity Apps Refresh • Proactive assistance • Force Touch • iPad Split View • Network & Security • Maps Enhancements • Apple OS 2 (9/16)
- 7. Proactive Assistance -Siri Gets Smarter • Enhanced voice commands • Contextual notifications & reminders • Browse through Apps via voice • New test cases • springboard control • Voice injection support required for testing Description Implications
- 8. Force Touch • TapticEngine implemented on iPhone 6S • Better Engagements (Email preview) • Already supported on MacBook's • Desktop & Mobile Capabilities Consolidation • New test cases • Access to Device Context is critical • Fragmented scenarios between iPhone 6S and earlier iPhones Description Implications
- 9. Public Transit/Maps App •Enhanced Maps application – Voice based instructions – ‘Nearby’ feature with recommendations • Environment conditions to be covered • How this feature works in various networks, locations (travel) • Notification relevancy Description Implications
- 10. Network & Security •iPV6 as a new app submission requirement to App-Store – Many carriers supporting iPV6 only networks – “Apps should probably work OOB on both iPV4 & iPV6” • Apple recommends that developers: – Use the networking frameworks – Avoid using iPV4 specific API’s – Avoid hard-coded addresses Description Implications
- 11. Apple Pay IsBecoming More Mature • More payment cards supported • App can be launched from Home screen • New “Wallet” app • Security tests • Testing across networks and locations • New test cases required • Balance • Reward card data representation Description Implications
- 12. Meaning Of NewiOS Device & OS Platforms Top 4 Implications 1. Environment & Lab 2. Test code maintainability 3. Platform robustness & quality 4. New test cases & branching
- 13. Meaning Of NewiOS Device & OS Platforms Environment & Lab • Evolve device coverage – 3-6 MUST devices added • iPhone 6S, 6S Plus – 9/25 • iPad Pro (12.9’’) - November • Coming Soon: iPad Air 3, iPad Mini 4, iPhone 6C – Lab grows even w/o new features • Connectivity & Setup • Coverage in varying environments
- 14. Meaning Of NewiOS Device & OS Platforms: Test Code Maintenance • Regression to reveal glitches – Changes to test code and test object names – Look and feel compliance – Wrong data references across platforms • Include new tests into CI/SDLC coverage
- 15. Meaning Of NewiOS Device & OS Platforms: Platform Robustness • History shows stability issues – Multiple minor releases to test – App stability impacted by new platform – Test stability implications
- 16. Meaning Of NewiOS Device & OS Platforms: New test cases • Branching test code suites between iPhone 6S and older • Additional test cases to cover new features
- 17. Poll 2 –What were the main issues around test automation in previous release? • Sync issues in test runs • Branching automation across platforms • Object analysis across platforms • Broken CI process • Don’t know
- 18.
- 19. Summary Automation & CIease platform adoption Optimize your lab with relevant Devices Test cases Real environments Continuously test & monitor
- 20. Introducing Perfecto Mobile Dominantleader & visionary Strong Ecosystem Perfecto @ a glance Partnering with Enterprises to create better mobile apps faster with continuous quality “Perfecto Mobile marks shift in mobile apps QA with Continuous Quality Lab” 20 Setting the bar for market success • Founded in late 2006, Business HQ in Boston • Over 200 employees globally • Fortune 500 customer base
- 21. Thank You Please RememberTo Complete The Survey
Editor's Notes
- #3 Submit questions using the Q&A panel. We try to answer all questions during and after the presentation. Our experts do not have access to the chat interface Participate in the polls Your participation is critical to a relevant, meaningful discussion. Watch your email for a copy of the recording and slides Today’s presentation will be recorded and sent to you. Complete the survey following the presentation Your feedback helps us provide educational tools like this webinar.
- #5 iOS9 will be adopted very fast, if you have not yet tested on the beta versions – start testing on GA now! https://mixpanel.com/trends/#report/ios_8/from_date:-336,report_unit:day,to_date:-199
- #7 Apple is introducing many new features and capabilities, not all will cause immediate implications to your apps, however some will like Force touch, iPad split view, the network and security changes and the voice commands (PA) In addition note that each major release comes with its quality and stability issues
- #8 Voice based capabilities can enable more complex scenario’s for better EUE To better support and test these, you would need rich environment capabilities with system level control & voice injection as part of your test framework features.
- #9 Such capability will enable better EUE however for Dev/Testers it means full system level control together with new and complex test cases developed Also this will mean higher iOS device fragmentation since not all iPhone’s will support this capability (Branching)
- #10 Location based capabilities added to the platform toward higher engagement with the users. To test such capabilities like Nearby, a robust test environment lab is required with varying network condition and system level Apple is taking a page from Yelp with a new feature called Nearby, which shows you shops, restaurants, places to drink, and other types of businesses around you or near the destination you enter in the Maps search bar.
- #11 IPV6 technology with improved IP ranges and security is widely adopted by carriers (e.g. Verizon) and Apple acknowledges that and mandates support for this new protocol as an appstore submission criteria Run relevant test using your existing apps to check for compliance and leverage apple’s best practices such as avoiding hard-coded addresses in your Apps
- #12 From iOS8 to 9 Apple put a lot of effort to drive its payment technology adoption. In iOS9 we shall see more cards supported, apps enhanced and more geo coverage like the UK. From Dev/Test perspective, apps who support the payment capabilities will be required for more advanced level of security tests with more locations covered, more use cases covered
- #13 In addition to the general enhancement, there are 4 key implications which ought to be considered even without a line of code changes to your apps.
- #14 To your existing lab you now need 3 more devices Setting these up is not a trivial task both locally or with distributed teams, as well as when needing to cover varying network conditions Working with a CQL in the cloud removes these pains from your teams and allows them to focus on the quality aspect only.
- #15 For existing test cases/suites the Dev/test teams will need to run a full regression on the new platform and devices to check for issues both in the test cases and defects in the app under test. There can be few common pitfalls when testing against a new device or platform like object identification, wrong data references etc. Once test suites are stable they need to be re-connected to the daily/on-demand CI processes
- #16 Plan for schedule gaps to allow for minor releases from Apple in the first few months Monitor your app store reviews for platform related bugs which impact your app stability/functionality Check in between releases your test framework for compliance/regressions
- #17 For new features, allow for new test cases which impact your overall test cycle average duration Manage your branches for relevant features and device support