5 Most Common Bug Writing Errors: Day #5

Another of the fields you may be required to set when entering a new bug is the Assignee field. This determines who has responsibility for the bug once you have entered it.

Some companies set up their projects so that all new bugs go to one person in particular who then reviews and assigns them to the appropriate person. If this is the case, just make sure that the default Assignee is correct when you enter a bug.

Error #5:
Assigning Bug to the Wrong Person

• Have a list of which bugs get assigned to whom
• Assign your bugs to the appropriate person

Again, with any bugbase that remembers your most recent bug entry, be careful that you are not assigning every bug to the same person if they should be assigned to different people. People find it very frustrating to have each and every bug assigned to them if they shouldn’t be.

This forces them to figure out who the bug should be assigned to and interrupts their work. Assign your bugs to the correct person and be viewed as a Quality Professional.

In 5 Keys to a Bulletproof Bug we covered how to enter any bug with clarity and confidence. Now you are also armed with the information you need to avoid the most common pitfalls that hamstring most testers.

5 Most Common Bug Writing Errors

1. Not Enough Information
2. Unclear Reproducibility
3. Omitting the Expected Result
4. Selecting the Wrong Severity
5. Assigning Bug to the Wrong Person

You know what hazards to avoid and how to avoid them. I have given you the tools to succeed in your bug writing. Now it is up to you. Go forth boldly and dare to excel!

You can be discouraged by failure, or you can learn from it. So go ahead and make mistakes, make all you can. Because, remember that's where you'll find success - on the far side of failure.
~Thomas J Watson Sr.

Congratulations!