knowledge tester tips on bug reporting
TRANSCRIPT
Credits
• Testing Computer Software by Cem Kaner, Jack Falk and Hung Q Nguyen
• Lessons Learned in Software Testing by Cem Kaner, James Bach and Bred Pettichord
• Presentations of Mahboob Ihsan (one of my mentors in software testing)
• Power Point template and most of the images: http://www.hubspot.com/
The only purpose to report bug is to get it fixed.
“ “
AVOID CLUSTER BOMBSReport one problem at a time.
Cluster bombs are good at destroying enemies but not good to improve quality of the product.
Image from Pakistan Post
Mindful of your tone in reporting the bug. A report that irritates the programmer loses it’s chance of getting fixed quickly.
Be Polite to humans who made errors
Call people by their right name
If some one calls you by wrong name, you don’t like it. Same goes for application names, window names, menu names etc.
{ }7 is a lucky number
for steps to
reproduceL im i t the s teps to rep roduce to 7 . Leng thy s teps don ’ t encou rage the reader to g i ve i t
a t r y
Bug life cycle
• Never exaggerate your bugs. It will hurt your credibility.
• It does not mean that you should not be highlighting it. It means not following as if it is some thing personal.
DO NOT SHOUT, JUST REPORT
A well defined problem is half solved.“
“
Title of the bug is like a news headline.
It should grab attention and should have all needed for the reader
Title
Description
Steps to Reproduce
File Attachments
SHARE ALL THAT YOU HAVE
PROGRAMMERS ARE FRIENDS, NOT FOES
