Most of the times testers get irritated when developers reject there defects or when they reassign them to the testers for more information. Why do this happen? What is wrong with the posted defects? These are the questions which usually arises in a testers mind. Especially with the newcomers. Moreover, a lot of time is wasted for both testers and developers if the defects are not communicated properly.
The best solution to avoid this is by reporting the defect with all the necessary details, so that the developer can reproduce/understand the defect.
There are various benefits when the defects are reported effectively. Some of them are:
1. The communication between the tester and the developer decreases. So, no time is wasted.
2. The defects get fixed quickly.
3. The tester can reproduce the defect as per the steps during retesting of a defect. No confusion for a tester on seeing his own defect after a long time :)
The following are some of the ways to improve the quality of bug reporting:
1. Firstly, try to reproduce the defect. Note every step you perform in the report.
2. Note down your observations.
3. Take some screenshots/movies as applicable and attach them.
4. Provide the system info for any defects noticed due to some system configurations.
5. Take the image of the OS if possible.
6. Rename your screenshots/movies/attachments accordingly.
7. Give the descriptions of the attachments in the defects.
8. Last but not least, make sure that your defect is reviewed by your peer before you submit. This will help to post your defects in a very efficient way :)
