1. Do not report such bugs Software Quality Assurance
Telerik Software Academy

2. The Lectors Snejina Lazarova Dimo Mitev Product Manager
Talent Management System
Dimo Mitev
QA Architect
Backend Services Team

3. Bad Bug Report Example Vague ones which just report the symptom
"I just clicked and it crashes"
Results from the course?

4. Bad Bug Report Example (2)
Ones which just use adjectives instead of numbers
"System is really slow"
Results from the course?

5. Bad Bug Report Example(3)
Lack of legacy behavioral, baseline comparisons etc.
"it used to work ..."
"system is slower ( than???)"
Results from the course?

6. Bad Bug Report Example (4)
Bugs in which there is no effort to zero in on the root cause. No effort on removing the variables
Results from the course?

7. Bad Bug Report Example (5)
Bugs which do not mention the user impact, yes includes too techie bugs :)
"we are using uninitialized variables here… here… and here…"
Results from the course?

8. Bad Bug Report Example (6)
Bugs with poor reproducibility information
"happens sometimes"
Results from the course?

9. Bad Bug Report Example (7)
Bugs which just report the problems (and not the steps to reproduce or the manifestation/symptoms of the problems)
"feature send mail is broken"
Results from the course?

10. Bad Bug Report Example (8)
The usual deficient in information ones e.g. with no logs, no customer data info, no platform info, no SW/HW info etc.
Results from the course?

11. Bad Bug Report Example (9)
The "Best One"
Results from the course?

12. Bad Bug Report Example (10)
Description:
Error message is stupid.
Results from the course?

13. Bad Bug Report Example (11)
Expected result:
Error message is less stupid.
Results from the course?

14. Key points for good bug report
Clear and succinct title
Bad: Browser crashed
Good: Error 404: Page not found when clicking the Export button
Results from the course?

15. Key points for good bug report (2)
Is it Reproducible?
Bad: Leave it blank
Good: "Every time", "Occasionally", "Unable to Reproduce"
Results from the course?

16. Key points for good bug report (3)
Description
Summary – short overview
What happened – step by step
Results from the course?

17. Key points for good bug report (4)
Supporting information?
Bad: Leave it blank
Good: "This error happens for all event records that are fees, but works for event records that are campaigns"
Results from the course?

18. Key points for good bug report (5)
Actual results?
Bad: "It did not work"
Good: "Error 404: Access denied"
Results from the course?

19. Key points for good bug report (6)
Expected results?
Bad: "I expected it to work"
Good: "I expected to see a popup after clicking the Run button"
Results from the course?

20. Key points for good bug report (7)
Platform
Bad: "Windows"
Good: "Windows 7, Google Chrome m"
Results from the course?

21. Key points for good bug report (8)
Include the Screenshots/Attachments!!!
Results from the course?

22. Do not report such bugs