How to make sure your App isnt CrApp


Published on

A presentation targeted towards Year 12s explaining different App Testing Strategies.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

How to make sure your App isnt CrApp

  1. 1. App Testing Strategies Making sure your App isn’t crApp Gavin Jones Managing Director Christian Cook Research Director
  2. 2. What is going to be covered?  Testing: What, How, Why?  White Box Testing  Black Box Testing  Compatibility Testing  Distributing Your App  Testing Your App
  3. 3. Testing: What, How, Why?  Make sure your App works as intended  Testing is all about questions and answers  Your App has to work all of the time, not some of the time  1 million+ Apps in the iOS App Store & the Google Play Store2  Poor Apps get ignored – The App market is a cut-throat place  26% of the time customers never give the app a second try1  You should test everything thoroughly in different scenarios  On the other hand, testing needs to be cost-effective 1 First Impressions Matter! 26% of Apps Downloaded in 2010 Were Used Just Once 2 Number of available Android Applications
  4. 4. Image Credit:
  5. 5. White Box Testing Black Box Testing
  6. 6. White Box Testing  Types  Unit Testing  Integration Testing  Advantages  Making sure it works – programmatically  You can perform this during development  Disadvantages  Need to have thorough knowledge of the App code  It works, but does it work?
  7. 7. Black Box Testing  Types  System Testing – Does it do what it was set out to do?  Acceptance Testing – Client & Beta tests  Compatibility Testing – What devices will it work on?  Advantages  Can be tested by other people  Overall issues of the App can be identified & addressed  Disadvantages  Cannot perform it until White Box testing is finished  Much broader than White Box testing
  8. 8. Compatibility Testing
  9. 9. STYLECampaign - Mobile Email Testing Rig
  10. 10. Accessible at: Android Device Fragmentation 11,000+ devices
  11. 11. Accessible at: Open Device Labs
  12. 12. Compatibility Testing  Different Screen Sizes  Access to specific functions e.g. 3G, GPS, NFC  Operating System Versions  iOS6, iOS7  Android 2.3, 4.0+  Consumer Behavior e.g. Do they buy Apps on this platform?  Does it meet platform specific guidelines?
  13. 13. Accessible at: iOS Human Interface Guidelines 223 Pages!
  14. 14. Distributing your App  App Inventor has many ways to test/distribute your App  Emulator - Bad  USB  AI Companion  QR Code for APK  Save APK  There are other ways to distribute…
  15. 15. Testing your App  Develop a Test Plan – System Testing breakdown: Smoke Testing Sanity Testing Ad-hoc Testing Functional Testing Boundary Testing Usability Testing Compatibility Testing Performance Testing Error Handling Testing Online & Offline Testing Regression Testing …and many more
  16. 16. Testing your App  Create test cases & scenarios for each testing type ID Test Name Action(s) to perform Test Data Expected Result Actual Result Pass or Fail 001 Opening the App Open the App from the Home Screen N/A The App Opens The App Opens PASS 002 Close the App Close the App using the menu button N/A The App Closes The App Crashes FAIL 003 Input a long name Input long name into the name field on the edit profile view Christian ‘Cookie’ Cook The name fits The name gets truncated with ellipsis (‘…’) PASS 004 … 005 … 006 …