">
Struggling with quality of bug report?Posted by Fleek IT Solutions on February 25th, 2021 Being a top software testing company, we understand that, in today’s competitive world we are always running out of time, a good quality bug report from the QA team can reduce the iterations between developer and QA, and help improving the productivity of the whole team. As a result, it will reduce overall project cost and speed up the time to market. From a QA point of view, sometime the most frustrating situation is: when your bug is “rejected” by the developer, or marked as “not reproducible”, or marked as “incomplete”, or marked as “not an issue”, or marked as “working as expected”. Don’t get upset, better to spend time on identifying the problem in the bug report and look for the improvements. Common issues with bug reportThere are a few common issues which may provide an opportunity for a developer to reject your bug report. Sit back and check if you made any of these mistakes? 1. Incomplete steps to reproduce in your bug report How can you improve the quality of bug reportQuality bug should consist of all details which can help developer to quickly understand and debug the scenario. The required details in a bug report depend upon the nature of the bug, and QA should be smart enough to identify such details and attached the bug report. Here are some tips to make your bug report as a quality bug report: 1. Make sure your bug report title is straight enough to explain the exact problem to developers and other project stakeholders Challenge in providing quality bug reportDue to security reason, sometime clients are not open to provide access to the database and log files. In such scenario you can discuss with the client and explain the importance of access to the database and log files. You can also ask for the read-only access to the database at least. Don’t let lack of access as an excuse because If you don’t ask then it is always NO.
Like it? Share it!More by this author |