As long as there would be softwares there would be defects in the software and as long as Testers keep finding defects they would have to report it in some form known as Bug Report/Defect Report.
Aim to write a Bug report – is to get it fixed !
If Testers are not good at filing bugs then many serious issues can get unnoticed and ‘Rejected’ as the Developer looking at the Bug report finds it hard to figure out the Bug.
Following are few checklists that can be kept in mind while reporting bugs.
I. Its All In A Title – A bug should be easily identifiable through its Title. Keep it short and crisp yet descriptive.
II. Keep It Simple – Keep your description simple and yet understandable. Do not use sophisticated terms for which the developer has to literally follow a dictionary.
III. Tell Steps To Reproduce – Its just like story telling. Write the steps you followed to find the bug, if necessary add examples to strengthen the importance of a bug. Its a good practice to divide the story into ‘Actual’ and ‘Expected’ behavior.
IV. Provide Links And Screenshots – Take screenshot(s), label and decribe it showing exactly where the bug is, its good to provide a link say for any video created for the bug to show complex steps to reproduce; it indeed saves time.
V. Additional Information – Add notes here regrading any additional information that a developer needs to know and follow to find the exact bug, can mention to refer screenshot attached or the links for videos showing steps to reproduce.