Post is not focused on “How to write a Bug Report “. Although it is about Bug Reporting, but will talk about “How Not To Write a Bug Report“.
I was recently assigned a project wherein there were already QAs working for quite some time and have raised truck load of bugs in bug tracking tool. My main task was to thoroughly test the website that was already tested by other testers. But before I could proceed, I decided to go through the important bugs already raised by QAs in order to avoid duplicity.
While reading the bug reports, I realized the common mistake QAs made while raising the bugs. I noted most of the bugs reported were in “Rejected” state & others (marked “Important” / “Critical”) were raised in such a manner that the bugs were in “Open” state for quite some time now, thus increasing the defect’s age. As a result, application was leading nowhere, So, client decided to do away with current QA team before it gets worse.