Bug Reporting - It's Art..!!!

Bug reporting is an art, you have to explain the scenario which is causing failure and your explanation should be mild so that anyone can replicate it and can understand the bug.

I had a huge discussion with my colleague for how many information are needed for each bug? I have worked with many clients and QAs, everyone has to have an own theory. It little hesitates for junior tester because they are working with different QAs.

According to me, bugs should have following qualities.

1. Minimum description.
2. One liner summary.(Should be understandable)
3. Be Specific

Non-Reproducible Issues:

Name itself having a big terror. Developer and tester having a fear of these kinds of issues. If are going to file non-reproducible issues it should have a perfect description. Developer and co-tester should easily understand. If it is network activity indicator or blank skeleton screen then it should have error logs. It would be batter if tester can attach video also.

User Interface and button padding area

This type of issues should have one liner summary and appropriate screenshot. It would be awesome if tester can mention that data/value is not coming from either server or database or its just UI stuff.

End of the story bug report should be a high-quality document. Focus on writing good bug reports. Your effort towards writing a good bug report will not only save the resources of the company but also create a good relationship between you and the developers. Stay tuned for next article "Bug One liner Summary".