-

What’s a (good) bug?  My opinions

Definition: A formal means of communication about a perceived problem.

Audience: practically everyone!  developer, product manager, project manager, dev manager, testers, test manager, even VP, President depending on company size

Title: brief, to the point, but not too short, but says what’s wrong
bad: “search broken”
good: “searching for items with ampersands results in no search results”

Summary: longer, maybe abbreviated steps

Description (optional): longer narrative

Steps to Reproduce — specific steps that anyone should be able to follow

Time when observed — for coordinating with log files

Observed:
Expected: VERY IMPORTANT

Screen Shot(s)

Severity — what is the impact on functionality when it happens — pretty objective — from small function works strangely …  global data loss.

Priority — how important — a business decision

Component — in which part of the software or functionality is the defect found?

Attachments: input files