The Art of Bug Advocacy

Testers find defects and raise awareness about quality. What happens after the bugs are found can be any tester’s guess, though. Bugs may get delayed, postponed, go unnoticed or linger on due to lack of information.

In my article for Ranorex blog, I talk about how Testers need to champion the cause of their bugs in order to avoid unneeded delays in fixing defects that are important. At the same time, testers should maintain a distance to make it an impersonal and impartial experience. Testers need to master the art of bug advocacy!

Why is advocacy important?

Advocacy is basically pleading the case for a bug to be fixed. The testers who find the bugs are the ones who need to advocate for their bugs. It is important that they take a stand and voice their opinions.

Some bugs may not be deemed important from a business perspective, as they seem too small. But in reality, they may be blocking an important feature for a particular user group. On the other hand, some bugs may seem more critical than they truly are, and while fixing them may be important, it may not be the highest of priority.

Whatever the case, testers must aim to present the facts and data in such a way that decision-makers are able to make well-informed resolutions about the issue.

Communication is key

Advocating for anything is not a one-way street. It takes discussion, debate and reaching a consensus on key points to make a collective decision. This is where testers’ communication skill plays a key role. Testers need to have good communication, both verbal and written.

When writing bug reports, testers need to focus on providing every possible piece of information that can help the team in understanding and triaging the issue. Missing, incorrect or ambiguous details make the bug look less relevant and important and may lead to the issue being ignored or deferred. To stress the importance of the issue, testers should mark the correct bug severity and use a good, descriptive title.

Beyond this, if you observe that the bug you reported is being postponed or not looked at, you must be able to initiate a discussion or raise a point during a triage meeting. Good verbal communication skills include being able to present your argument, discuss the repercussions and reach a conclusion with the team in a professional manner.

How and when to advocate

Since more and more teams are following agile development methods, communication is mostly verbal, and triages are quick discussions of bugs found in a day or week within a sprint. A short, live demonstration of the issue is the best way to present the bug if the agile team is not using detailed bug reports. Read more –>

It’s not personal!

Bug advocacy is not about finger-pointing or blame games. Read more –>

Testers need to remember that it is not up to them to decide whether a bug gets fixed. The business makes the decision based on multiple factors, like the risk it poses, time constraints and budget. Testers can keep track of postponed or deferred issues and raise flags when the list grows beyond an expected number in order to escalate more bug fixes.

Read the full article here ->


2 thoughts on “The Art of Bug Advocacy

  1. In some organisations, the mot powerful bug advocacy argument is: “If the CEO sees this bug in release, will someone get sacked?”
    Surprising how often that concentrates minds, even for comparatively minor bugs. (What that says about that particular organisation is an entirely different matter.)

    Liked by 2 people

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s