As testers, we write bug reports to communicate important information to our business about potential problems that we've observed. We use an array of tools and techniques to uncover these problems, yet we often write our bug reports as an afterthought, thinking that the hard work has already been done. A poorly-communicated bug report can be as bad as failing to find the bug in the first place, if our business cannot understand the relative importance of an issue.
With developers and managers reviewing our bug reports and forming an impression of our testing skills based upon the information within, taking the time to consider what makes an effective bug report is an important step to ensuring that you hold credibility within your team.
In this video, we will look at how clear linguistic usage, persuasive techniques and phrasing problems in terms of their user impact can help to make our bug reports more effective. You'll also see how Michael Bolton's "PEOPLE WORKing" heuristic can serve as a valuable mnemonic for evaluating the effectiveness of our bug reports.