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.

SEERS - Standardised Bug Reporting

1,215 views

Published on

SEERS is a standardised method of reporting bugs and defects - ensuring consistency and efficiency in your testing and development team.

Published in: Technology
  • Be the first to comment

SEERS - Standardised Bug Reporting

  1. 1. SEERS Standardised Bug Reporting Antony Kennedy @booshtukka antony@silversquid.com
  2. 2. The first computer bug. Ever.
  3. 3. Different testers raise different bugs in different ways.
  4. 4. Different testers raise different bugs in different ways.
  5. 5. What is a poor tester to do?
  6. 6. Introducing:
  7. 7. Introducing: SEERS
  8. 8. • Screenshot
  9. 9. • Screenshot • Environment
  10. 10. • Screenshot • Environment • Expected/Actual Behaviour
  11. 11. • Screenshot • Environment • Expected/Actual Behaviour • Reproduction
  12. 12. • Screenshot • Environment • Expected/Actual Behaviour • Reproduction • Severity
  13. 13. Benefits of SEERS
  14. 14. Benefits of SEERS • Ensuring consistent error reports
  15. 15. Benefits of SEERS • Ensuring consistent error reports • (even with new staff)
  16. 16. Benefits of SEERS • Ensuring consistent error reports • (even with new staff) • The capturing of all relevant information
  17. 17. Benefits of SEERS • Ensuring consistent error reports • (even with new staff) • The capturing of all relevant information • Less confusion
  18. 18. Benefits of SEERS • Ensuring consistent error reports • (even with new staff) • The capturing of all relevant information • Less confusion • Greater efficiency
  19. 19. Benefits of SEERS • Ensuring consistent error reports • (even with new staff) • The capturing of all relevant information • Less confusion • Greater efficiency • Profit!
  20. 20. Screenshot There should always be a screenshot of the problem. Mac software: • skitch.com • Grab Windows software: • www.screenshot-utility.com • alt-print screen
  21. 21. Environment There should always be details on the environment the problem occurred in. Don’t forget: • Browser (including version) • Operating System • Screen Resolution
  22. 22. Expected/Actual Behaviour There should always be details on what happened, and exactly what was expected to happen.
  23. 23. Reproduction There should always be accurate details on how to reproduce the bug.
  24. 24. Severity There should always be details on how severe the problem is. i.e. How important it is that we fix it.
  25. 25. Graded Browser Support Which browsers should we support, and to what degree?
  26. 26. Grades • Grade A These browsers should work perfectly (with progressive enhancement), look close to perfect and perform well. • Grade B These browsers should work acceptably, look good and perform well. • Grade C These browsers should work and have no obscured or illegible content.
  27. 27. Grade A Browsers • Windows XP/Vista/7 - IE7 IE8 - - Firefox 3.5 - Opera (latest version) - Safari (latest version) - Chrome (latest version) • Mac OSX 10.5/10.6 - Safari (latest version) - Firefox 3.5 Opera (latest version)
  28. 28. Grade B Browsers • Windows XP/Vista - Firefox 3 IE6 - • Mac OSX 10.5/10.6 - Safari (previous version) - Firefox 3
  29. 29. Grade C Browsers • Everything else!
  30. 30. Yahoo!’s Graded Browser Support http://developer.yahoo.com/yui/articles/gbs/
  31. 31. The Five Paths Paths describe the route a user takes through our site.
  32. 32. • The Happy Path
  33. 33. • The Happy Path • The Typical Path
  34. 34. • The Happy Path • The Typical Path • The Unhappy Path
  35. 35. • The Happy Path • The Typical Path • The Unhappy Path • The Insane Path
  36. 36. • The Happy Path • The Typical Path • The Unhappy Path • The Insane Path • The Evil Path
  37. 37. The Happy Path The user does exactly what we expect them to. Grade A browser.
  38. 38. The Typical Path The user does reasonable things that we expect them to. Grade A browser.
  39. 39. The Unhappy Path The user does things we do not expect them to. Grade A or B browser.
  40. 40. The Insane Path The user is completely insane and clicks things at random (probably whilst humming themes to 80s TV shows and shouting “CRUSH IT”). Any grade browser.
  41. 41. The Evil Path The user is trying to break our site. This person is probably a tester or a hacker. Any grade browser.
  42. 42. Severities Is it worth fixing?
  43. 43. • Blocker
  44. 44. • Blocker • Critical
  45. 45. • Blocker • Critical • Major
  46. 46. • Blocker • Critical • Major • Minor
  47. 47. • Blocker • Critical • Major • Minor • Trivial
  48. 48. Blocker The piece of functionality we have built does not work correctly when the user is on the Happy Path. A user on the Evil Path is able to cause damage or view private data. No further testing can occur. We can not release.
  49. 49. Critical The piece of functionality we have built does not work correctly when the user follows the typical path. We can not release.
  50. 50. Major The piece of functionality we have built does not work correctly when the user follows the unhappy path, content is obscured or, functionality is inaccessible. We should not release.
  51. 51. Minor The piece of functionality we have built does not work correctly when the user follows the insane path, or there are cosmetic issues with Grade B browsers. We can release.
  52. 52. Trivial There are minor cosmetic issues with Grade B or C browsers. We should release.
  53. 53. Terminology What is a bug and what is a defect?
  54. 54. A Bug A bug is a problem found with functionality we have recently developed that is being tested.
  55. 55. A Defect A defect is a problem we have found that is not related to current work.
  56. 56. SEERS
  57. 57. SEERS • Screenshot
  58. 58. SEERS • Screenshot • Environment
  59. 59. SEERS • Screenshot • Environment • Expected/Actual Behaviour
  60. 60. SEERS • Screenshot • Environment • Expected/Actual Behaviour • Reproduction
  61. 61. SEERS • Screenshot • Environment • Expected/Actual Behaviour • Reproduction • Severity
  62. 62. Use SEERS. Save time. Fix bugs properly.
  63. 63. Thank you! Antony Kennedy @booshtukka antony@silversquid.com
  64. 64. Thank you! www.zeroedandnoughted.com Antony Kennedy @booshtukka antony@silversquid.com

×