Follow up on Bug Investigation

Earlier in this space, I wrote an entry about Bug Investigation. But there is an important component I did not even begin to talk about – bug advocacy.

Bug advocacy means making stakeholders want to fix the bugs you find by finding effective ways to communicate. It might mean overcoming objections, motivating stakeholders with “salesmanship,” and researching new context about what you found.

“The best tester isn’t the one who finds the most bugs or embarrasses the most programmers,” says Dr. Cem Kaner, Professor of Software Engineering at the Florida Institute of Technology. “The best tester is the one who gets the right bugs fixed.”

Cem is the principal author of a course titled “Black Box Software Testing” and has given me permission to post the following links to his course material involving bug advocacy:

http://www.testingeducation.org/BBST/slides/BugAdvocacy2008.pdf

Videos:

http://www.testingeducation.org/BBST/videos/BugAdvocacy2008A.wmv

http://www.testingeducation.org/BBST/videos/BugAdvocacy2008B.wmv

http://www.testingeducation.org/BBST/videos/BugAdvocacy2008C.wmv

http://www.testingeducation.org/BBST/videos/BugAdvocacy2008D.wmv

http://www.testingeducation.org/BBST/videos/BugAdvocacy2008E.wmv

http://www.testingeducation.org/BBST/videos/BugAdvocacy2008F.wmv