10 things to avoid in your software bug report

1,643 views
1,261 views

Published on

Writing accurate and effective bug report is a key responsibility for software testers and quality engineers. This presentation contain some basic tips tip consider while reporting bugs.

Published in: Technology
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,643
On SlideShare
0
From Embeds
0
Number of Embeds
32
Actions
Shares
0
Downloads
41
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

10 things to avoid in your software bug report

  1. 1. By: Belal Raslan (Quality Consultant) Quality Partners™ www.sq-partners.com © 2014, Quality Partners™
  2. 2. How to write effective Bug report 1. Report the pattern not an example. 2. Don’t describe what's wrong, only! 3. Be direct to the point (don’t tell a story!). 4. Report the bug, but not how to solve it. 5. Don’t mix between priority and severity. 6. Don’t use: CAPS, red letters, red circles, ‘!’ , ‘?’. 7. Don’t use your personal judgment. 8. Make your description understandable for everyone. 9. Minimize the options. 10. Don’t use the word ‘Sometimes’. (C) 2014, Quality Partners™ •2
  3. 3. How to write effective Bug report 1. Report the pattern not an example. Avoid this: When multiplying -2 by 3 then answer will be positive. (C) 2014, Quality Partners™ •3
  4. 4. How to write effective Bug report 2. Don’t describe what's wrong, only! Avoid this: When adding a new item, the items list will be ordered alphabetically. (C) 2014, Quality Partners™ •4
  5. 5. How to write effective Bug report 3. Be direct to the point (don’t tell a story!). Avoid this: Open your browser, type the site URL, go to home page, login as user, go to ‘add item’, you’ll find the first field ‘usernam’ misspelled. (C) 2014, Quality Partners™ •5
  6. 6. How to write effective Bug report 4. Report the bug, but not how to solve it. Avoid this: The ‘ID’ field in the report is incomplete, please define the ID in the data base as integer of (10). (C) 2014, Quality Partners™ •6
  7. 7. How to write effective Bug report 5. Don’t mix between priority and severity. Avoid this: The client name in the report is misspelled. Priority: High, Severity: High (C) 2014, Quality Partners™ •7
  8. 8. How to write effective Bug report 6. Don’t use: CAPS, red letters, red circles, ‘!’ , ‘?’. Avoid this: The tax calculation formula is INCORRECT !!?? (C) 2014, Quality Partners™ •8
  9. 9. How to write effective Bug report 7. Don’t use your personal judgment. Avoid this: I don’t think that the home page UI design is nice. (C) 2014, Quality Partners™ •9
  10. 10. How to write effective Bug report 8. Make your description understandable for everyone. Avoid this: Reference to our discussion today, please do the needed action for this page. (C) 2014, Quality Partners™ •10
  11. 11. How to write effective Bug report 9. Minimize the options. Avoid this: Page background color should be blue or orange or green or you can make it black or even white. (C) 2011, Quality Partners™ •11
  12. 12. How to write effective Bug report 10. The golden rule: Don’t use the word ‘Sometimes’. Avoid this: Sometime the tax calculation formula is not working as expected. (C) 2011, Quality Partners™ •12
  13. 13. 7 reasons why testing should start early in the SDLC Author: Belal Raslan (Quality Consultant) Email: Braslan@sq-partners.com Twitter: @BelalRaslan •13

×