Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

10 Best Practices for bug-free Apps & Websites

8,187 views

Published on

[Webinar Frenchweb]

1. Identify the product risks
2. Think UX
3. Define target devices
4. Think product specifics
5. Use the best resources to track bugs
6. Opt for the appropriate test methodology
7. Analyse bugs
8. Listen to your users
9. Follow the development of the digital ecosystem
10. Think testing

Published in: Devices & Hardware
  • Login to see the comments

10 Best Practices for bug-free Apps & Websites

  1. 1. 10 Best Practices For Bug-free Apps & Websites*
  2. 2. We only have one chance to make a good first impression! GOAL: ZERO BUGS* * Zero risk does not exist as it is impossible to test everything. Therefore, testing must be targeted. How to target and organise your tests? Discover the 10 best practices to adopt.
  3. 3. BUG HUNTERS QUALITY ASSURANCE EXPERTISE Member of TEAM TESTERS QA ANALYSTS QA MANAGERS +2,000 DEVICES StarDust, the Digital Testing specialist, supports its clients in the transformation and success of their digital solutions. OFFICES MARSEILLE, PARIS, LILLE MONTREAL (LONDON, BERLIN)
  4. 4. EFFORT-BASED QAFULL SERVICE QA STARDUST PARTNER PROGRAM > A macro-budget generator to help you plan testing budgets > Guidelines to help you best plan your UAT phases > Discounts according to your Partnership level Outsourcing the execution of tests > Defining the best fitted testing Strategy > Writing the StarDust Acceptance Test Plan > Delivering Bug reports > Delivering Test Results Analysis OUR SERVICE OFFERS For Digital Agencies Outsourcing a testing project > Giving you the lead on our testers > Delivering Bug reports
  5. 5. WHY TEST? TO BETTER CONTROL THE RISKS RELATED TO DEVELOPMENT TO TEST PRODUCT LIMITS TO ENSURE OPTIMUM FUNCTIONALITY TO ENSURE QUALITY TO REDUCE RISKS AT THE LAUNCH TO FIND BUGS and fix them TESTING
  6. 6. + 1 500 characteristics by device OS versions, middleware and frameworks ONGOING EVOLUTIONS (devices, OS, browsers…) CAUSES : A FRAGMENTED TECHNICAL ENVIRONMENT, PERMANENTLY EVOLVING + ONGOING EVOLUTIONS OF DIGITAL HABITS+ + BUGS
  7. 7. BUGS Missing product image (MAC OSX) Display of « feedback » button is unreadable (iPad Mini 2) Display of Social Media buttons (Safari MAC)
  8. 8. BUGS Pop-up doesn’t close > impossible to proceed to payment (iPhone 4S) Basket page greyed > no action possible (iPad Air) ???? (Macbook Safari)
  9. 9. BUGS Inconsistency between the number of products in the basket (5) and in the list (4) (Safari) Missing products and information (Chrome) Incomprehensible display (iPhone 5S)
  10. 10. BUGS ET ANOMALIES ! A device that does not pass the identification step in the purchasing process Failure to add product to cart Search button that cannot find queries Failure to validate postal addresses in login/sign up forms Different product/price between the cart and purchasing process Failure to take into account promotional discounts Ogone Payment accepted without typing in credit card n° (!!) Banking information impossible to fill in on mobile Deteriotated display blocking the purchase Common bugs seen on E-commerce apps and websites BUGS And…
  11. 11. BUGS Regardless of the bug, when the experience was bad or found to be unsatisfactory, the user loses FAITH and condemns the brand. CONSEQUENCES : BAD USER EXPERIENCE ABANDONED CHECKOUTS NEGATIVE FEEDBACK (E-REPUTATION) LOOSING CLIENTS / THUS REVENUE BRAND IMAGE DETERIORATION …… ……
  12. 12. BUG HUNTERS QUALITY ASSURANCE EXPERTISE Member of TEAM TESTERS QA ANALYSTS QA MANAGERS +2,000 DEVICES StarDust, the Digital Testing specialist, supports its clients in the transformation and success of their digital solutions. OFFICES MARSEILLE, PARIS, LILLE MONTREAL (LONDON, BERLIN)
  13. 13. IDENTIFY THE PRODUCT RISKS 1
  14. 14. 1. IDENTIFY THE PRODUCT RISKS Which, in case of a bug, impedes the use of the product. Examples of critical functions: PURCHASE TUNNEL PRODUCT PAGE DELIVERY CUSTOMER SERVICES REFUNDS …. KNOW YOUR PRODUCT List the technical functions What are the critical functions ? In what form? Examples of documents/formats: FUNCTIONAL SPECIFICATIONS USER STORIES BACKLOGS WIREFRAMES / MOCK-UPS …
  15. 15. THINK USER EXPERIENCE 2
  16. 16. 2. THINK USER EXPERIENCE THROUGHOUT the DEVELOPMENT process of your product Product Profit(s) Ergonomics / Design Is my website/app user-friendly?Does my website/app fulfil promises made to the user? Omni-channel / multi-device experience Unique / personalised experience Does my website/app take into account the profile and preferences of my users? Is the user experience optimal at all times and on all screens?
  17. 17. DEFINE TARGET DEVICES 3
  18. 18. 3. DEFINE TARGET DEVICES MARKET DATA Device Sales Traffic / Usage Comments FRAGMENTATION Overlay, Browser CPU, Arch, Memory Screen sizes Resolution sensors PROJECT’S TECHNICAL REQUIREMENTS OS versions Resolutions Equipment Resources Type of project 90-95% COVERED RISKS SITE : 25-30 Devices APPS : 30-40 Devices PRIORITY TO YOUR USERS’ DEVICES
  19. 19. THINK PRODUCT SPECIFICS 4
  20. 20. 4. THINK MOBILE SPECIFICS > OS Specifics > Browser Specifics > Multi-tasking: one rarely uses one application at a time > Texts / Calls / Notifications Interruptions > Memory & Backup Vertical / Horizontal Touch Navigation Wi-fi VS 3G/4G External AppConnection Think Mobile-first: your users are mobile! MULTI-PLATFORM & MULTI-SCREEN
  21. 21. USE THE BEST RESOURCES TO TRACK BUGS 5
  22. 22. 5. USE THE BEST RESOURCES TO TRACK BUGS DEVICES > Owning the most representative devices + some « exotic » devices > Renew the stock (new devices, new OS) > Maintain the old OS versions > Manage obsolete devices > Bring your own device (BYOD) > QA EXPERTISE > IMPARTIALITY > TIME SAVING INDEPENDENT TESTERS TESTERS > Internal testing team or > Outsourcing testing phases DEDICATED PEOPLE MATERIAL TOOLS / SUPPORT > Test plan > Bug tracker
  23. 23. OPT FOR THE APPROPRIATE TEST METHODOLOGY 6
  24. 24. 6. OPT FOR THE APPROPRIATE TEST METHODOLOGY Manual or automated tests? SCENARIO APPROACH > Writing test scenarios > Guided tests according to testing steps > Maximized risk coverage Stability of the test environment is important Developments must be « frozen » during the tests to guarantee the consistency and reliability of the obtained results Scenario or exploratory testing? EXPLORATORY APPROACH > No predefined testing scope/ random exploration > Reporting a maximum of bugs within a given time > Tester experience / UX expertise MANUAL > Stick as closely as possible to real behaviour > Test the real user experience > Control the complicated test cases AUTOMATED > Defining scripts and paths for automated tests (necessary time for creating scripts are to be expected)
  25. 25. ANALYSE BUGS 7
  26. 26. 7. ANALYSE BUGS > To understand the critical points of the website/app > Think maintenance/ product regression > List all the bugs and describe them in detail: Bug category, its description, screenshots, devices, steps to reproduce the bug GATHER BUG INFORMATION PROCEED TO ADJUSTMENTS THINK OF RE-TESTING Using the same methodology On the same terminals Use a Bug Tracking Tool ANALYSE
  27. 27. LISTEN TO YOUR USERS 8
  28. 28. 8. LISTEN TO YOUR USERS SALES MARKETUSERS FEEDBACKS FEEDBACK & ANALYTICS Comments / notes Social networks Surveys Pushes Real-time chat Eye tracking ... Traffic Downloads Conversion rate … New needs Innovation Top sales …
  29. 29. FOLLOW THE DEVELOPMENT OF THE DIGITAL ECOSYSTEM 9
  30. 30. 9. FOLLOW THE DEVELOPMENT OF THE DIGITAL ECOSYSTEM New product features New OS / browsers Autumn 2015 iOS 9, Android 6.0, Windows 10, Edge iPhone 6S UPDATES ANTICIPATE THE DEVELOPMENTS / THINK MAINTENANCE NEWS NEW RISKS New devices New OS …
  31. 31. EFFORT-BASED QAFULL SERVICE QA STARDUST PARTNER PROGRAM > A macro-budget generator to help you plan testing budgets > Guidelines to help you best plan your UAT phases > Discounts according to your Partnership level Outsourcing the execution of tests > Defining the best fitted testing Strategy > Writing the StarDust Acceptance Test Plan > Delivering Bug reports > Delivering Test Results Analysis OUR SERVICE OFFERS For Digital Agencies Outsourcing a testing project > Giving you the lead on our testers > Delivering Bug reports
  32. 32. 10. THINK TESTING What features? Depending on which user scenarios? On which terminals? What types of tests? DEVELOP A TEST STRATEGY Think ‘TESTING’ as soon as possible in the product life cycle WHAT? WHEN? Integration tests / System tests / UAT phases At the end of development? At the end of each sprint? Maintenance WHO? HOW? Internal dedicated testers? Outsourced independent testers? Which test methodology? Manual / automated tests?
  33. 33. THANK YOU François Joseph VIALLON, CEO StarDust www.stardust-testing.com “Quality is remembered long after the price is forgotten” Guccio Gucci

×