Your SlideShare is downloading. ×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Technology: Assuring Quality in an Agile Mobile World

278

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
278
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
15
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Having your mobile application fail….Negatively impacts revenueHurts your brandResults in rework instead of enhancementImpacts team moralWhat is failure in the mobile space?
  • We can argue Platform Applevs Android all we want, but what’s really important….
  • Deliver New Capabilities Instead of Fixes Prove it Works! Prove it Works Well! Prevent Damage to your Brand! Increase User Retention!
  • Growth is projected to be HUGE.Pundits are projecting 30 Million iPad sales this holiday season.
  • Small investment to generate revenue Quick to market as Apps are Focused Solutions Employing Agile Delivery Methods Rapid feedback loops Easy access to customer metrics Have an ideaWrite some code (test it….hopefully)Customer use it and provide feedbackFix bugs and enhance featuresRepeat steps 2 through 4
  • Need visualization of this stuff
  • Dev sees this model as too much control/process, in efficientzzQA practitioners view the well trained horse as a better modelBehavior is predictableControls have been established and are know to horse & rider
  • Development Cowboys riding in rodeoQA in Agile is like trying to hold the tail of a bucking bronco
  • Working together to sprint to the finishQA Knows a thing or two that can be applied to the Mobile Agile world
  • Plan – Agree on what is important to test, who will test and how to test itDesign – Build tests & test data (manual or automated)Execution – Did you accomplish what you set out to do? Prove it.Reporting = Retrospective
  • What Happened in the Past Create and Forget Documentation Turgid bloated document outlining Scope of test Approach & Plan Schedule Resource Risks Plans Change Once Work Starts
  • How do we do it in an Agile Approach Release Planning Resource Plan (people, devices, tools, $$) Test Strategy Estimated Schedule Sprint Planning Resources Scope (tasks) Acceptance Criteria
  • Get Test Devices: Native apps often need devices for testing / Mobile Web can leverage service test models, though devices are a good practicesBuild Test System: Backend systems are needed to support testing and fall to more traditional testing modelsBuild Test Harnesses: Test your backend before it is integrated with the front end. Speeds up delivery Map Poor Cell Coverage Areas: Cell based and location services cannot be simulated well in a lab environment: Get out in the world!Engage Crowd Source Testing Company – Don’t buy, borrow! Increase the diversity of devices, user experiences & locations(Cellular/WIFI) – However, difficult to protect secret app! Get Microwave Oven (no Signal Condition): Aside from feeding the team, a Microwave is a great tool for shielding devices from cell/wifi signals. Different than turning off signal in device Create Test DataCreate Test Scenarios/CasesBuild Test Automation
  • http://googletesting.blogspot.com/2011/09/10-minute-test-plan.htmlJames Whittiker10 minutes is actually 30 minutesAssess riskIdentify PrioritiesNon-technical approach Matrix of Mobile Solution Attributes vs Application Components/FeaturesQuantifies Capabilities for each Attribute/Component intersection with high # indicative of higher risk (therefore more testing needed)
  • Simulator/Emulator don’t work
  • Agile engages the users/customer early and often, so we avoid the classic challengesLimited User InvolvementNo Feedback until whole solution is completeAgile uses:Sprint DemoUser Story Acceptance Criteria
  • Quality Assurance is achieved by best practices and continuous improvement
  • Transcript

    • 1. FAILURE SUCKS! ©2012 MOBCON ─ WHERE MOBILE MINDS CONNNECT. ALL RIGHTS RESERVED. 2
    • 2. PLATFORM WARS ©2012 MOBCON ─ WHERE MOBILE MINDS CONNNECT. ALL RIGHTS RESERVED. 3
    • 3. WHY ASSURE QUALITY?• Deliver New Capabilities Instead of Fixes• Prove it Works!• Prove it Works Well!• Prevent Damage to your Brand!• Increase User Retention! ©2012 MOBCON ─ WHERE MOBILE MINDS CONNNECT. ALL RIGHTS RESERVED. 4
    • 4. ©2012 MOBCON ─ WHERE MOBILE MINDS CONNNECT. ALL RIGHTS RESERVED. 5
    • 5. MOBILE LIFE CYCLE Get Feedback Build It!Have an Idea Fix/Enhance ©2012 MOBCON ─ WHERE MOBILE MINDS CONNNECT. ALL RIGHTS RESERVED. 6
    • 6. WHAT CAN GO WRONG?• App Doesn’t Deliver Promised Functionality• App Crashes• App is Buggy• Coding Issues Cause Secondary Issues • Runaway Memory Usage • App Drains Battery• Customers Reject Design ©2012 MOBCON ─ WHERE MOBILE MINDS CONNNECT. ALL RIGHTS RESERVED. 7
    • 7. HOW DEVELOPERS VIEW TRADITIONAL QA ©2012 MOBCON ─ WHERE MOBILE MINDS CONNNECT. ALL RIGHTS RESERVED. 8
    • 8. HOW QA VIEWS DEVELOPERS ©2012 MOBCON ─ WHERE MOBILE MINDS CONNNECT. ALL RIGHTS RESERVED. 9
    • 9. AN EFFECTIVE AGILE TEAM ©2012 MOBCON ─ WHERE MOBILE MINDS CONNNECT. ALL RIGHTS RESERVED. 10
    • 10. QA LIFE CYCLE • Plan: Who, What, Where, W hen and How • Design: Build Tests & Data • System Test: Technical Tests • UAT: Business User Tests • Reflect: Improve for Next Time ©2012 MOBCON ─ WHERE MOBILE MINDS CONNNECT. ALL RIGHTS RESERVED. 11
    • 11. TEST PLANNINGWhat Happened in the Past ©2012 MOBCON ─ WHERE MOBILE MINDS CONNNECT. ALL RIGHTS RESERVED. 12
    • 12. TEST PLANNING Release Plan How Agile Does It Sprint Sprint Sprint SprintProduct Backlog Release Planning Meeting Sprint Scrum Board Backlog To Do In Done Progress Sprint Planning Meeting ©2012 MOBCON ─ WHERE MOBILE MINDS CONNNECT. ALL RIGHTS RESERVED. 13
    • 13. QA TASKS Build Map EngageGet Test Build Test Poor Cell CrowdDevices Test System Coverage Source Harness Areas TestingGet Create Create Provision Build TestMicrowave Test Test Test AutomationOven Data Cases Devices ©2012 MOBCON ─ WHERE MOBILE MINDS CONNNECT. ALL RIGHTS RESERVED. 14
    • 14. GOOGLE “10 MINUTE” TEST PLAN1. Attributes the adverbs and adjectives that describe the high level concepts testing is meant to ensure. Attributes such as fast, usable, secure, accessib le and so forth.2. Components the nouns that define the major code chunks that comprise the product. These are classes, module names and features of the application.3. Capabilities the verbs that describe user actions and activities. ©2012 MOBCON ─ WHERE MOBILE MINDS CONNNECT. ALL RIGHTS RESERVED. 15
    • 15. TEST DESIGNUser Story Acceptance• Happy Path• Negative Scenarios• Adhoc Testing …….. but with a Plan ©2012 MOBCON ─ WHERE MOBILE MINDS CONNNECT. ALL RIGHTS RESERVED. 16
    • 16. EMBEDDED DEVICE TESTING • Chip Dependencies • GPS/Location Service • Accelerometers • NFC • WIFI/Cellular • Memory Management ©2012 MOBCON ─ WHERE MOBILE MINDS CONNNECT. ALL RIGHTS RESERVED. 17
    • 17. TEST AUTOMATION Robot Testing Army MVC Automation ©2012 MOBCON ─ WHERE MOBILE MINDS CONNNECT. ALL RIGHTS RESERVED. 18
    • 18. USER ACCEPTANCE TESTING ©2012 MOBCON ─ WHERE MOBILE MINDS CONNNECT. ALL RIGHTS RESERVED. 19
    • 19. REFLECT ©2012 MOBCON ─ WHERE MOBILE MINDS CONNNECT. ALL RIGHTS RESERVED. 20
    • 20. QUESTIONS ©2012 MOBCON ─ WHERE MOBILE MINDS CONNNECT. ALL RIGHTS RESERVED. 21

    ×