Posted by tac_admin, June 3, 2011

What is Most Important When Reporting Defects?

Analysts – what do you think is the most important piece of information to include when reporting a defect found during testing?


4 responses to “What is Most Important When Reporting Defects?”

  1. Joy Somers says:

    Details, details, details. Enough information to articulate the expected behavior, details so recreation of the defect is easily identified, and screen shots. “Tell completely, show completely”

  2. Teresa Bennett says:

    Very good points Joy – To effectively test, details are important in every aspect of the testing process.

    This is covered in great detail in my eBook “What Makes a Good Software Tester a Great Software Tester”. You can purchase that book and download it directly from this site or on Amazon for Kindle apps.

  3. Jo Keown says:

    I always capture details about what the test result should be, what the result was, how the user entered the data, and what data was entered. If an error message was displayed during the testing, include a screen shot of the message (preferably showing the context) and describing at what point of the transaction the error message appeared. Then I walk the developer through the testing scenario so they can see/replicate the issue.

    I include all this information on a non-conformance register (or helpdesk system) that can capture both text and images. I have been using Word for this, but in the future I will be using RT (Request Tracker), which is freeware and really powerful.

    • Teresa Bennett says:

      This is great info Joanne – thanks for sharing! Details, test data, results are all important things to include. I’m going to check out Request Tracker, I’m always on the look-out for tools I can share with my clients and readers.

Leave a Reply

Your email address will not be published. Required fields are marked *

Get in touch today

Speak directly with The Analyst Coach
and get pointed in the right direction.





Preferred Contact EmailPhone

Subscribe to receive our free white paper on how weak requirements effect strong companies




tesra-circleanalyst

Sign up to get your FREE Business Analyst Survival Guide

Don't worry, we hate spam too. We will never share your information to third parties.