The Right Scenario for Reporting a Bug in Repro Steps

reporting software bugThe main problem developers often encounter is incorrect bug description in the report by the testers. For example, misplacement of the bug description creates chaos instead of leading to solution. Developers have to find out if the described situation is a bug, is it needed for the bug to appear? Is it just a condition of the bug existence? Or is it a simple customer mistake, as it often comes out.

Please be aware that the bug should be described according to the simple rules, with mentioning the bug in the Expected Results section, not in the Repro Steps section of your report. In addition to creating mischief this makes you doing excessive and unneeded actions, i.e. mentioning the bug twice.

What is the solution then? Creating a clear and correct report with understandable bug description placed in the right section of your bug report. Let’s take a closer look on some examples.

Incorrect format:

Repro Steps:

  1. Creating a new order
  2. Adding an item to it
  3. Clicking Delete button should delete the order
  4. It actually doesn’t

Expected Results: The order should be deleted

Actual Results: The order does not do what it should

Correct Format:

Repro Steps:

  1. New order is created
  2. Item is added to it
  3. Clicking Delete button should delete the order

Expected Results: The order should be deleted

Actual Results: The order does not do what it should

As you see, the difference is great, both in quality and quantity of information provided. If you do the things the right way it results in finding the solution and fixing the bug much sooner.

VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

    Tagged:


    Facebook Comments

    comments

    'The Right Scenario for Reporting a Bug in Repro Steps' have 2 comments

    1. Author Image

      August 20, 2013 @ 1:15 pm Joe

      I agree that correct steps are important, but the steps to reproduce should only include actions, not predictions. In this example step 3 should only be “Click Delete” and nothing else. The expected behavior is already covered by the next part, so no reason to include that in the repro steps.
      That said, repro steps only describe the actions. There is way more that needs to disclosed to developers for them to reproduce the issue. That includes build number, environment, location of database (the code may be fine if it is a data issue, or the code in a different context is broken), and so on.

      Bug Report
      Repro steps
      1. Read post in QArea blog “The Right Scenario for Reporting a Bug in Repro Steps”

      What happens
      Many questions are left open, steps in the “Correct Format” section are not as correct as they should be

      What should have happened
      Should have posted more detail and give correct examples on how to properly report a bug.

      Reply

    2. Author Image

      August 23, 2013 @ 10:04 am Mike

      Hello, my version of the above – Correct Format example is as follows

      Repro Steps:

      1. Select to create a new order
      2. Add an item to it
      3. Click Delete button

      Expected Results: The order is deleted

      Actual Results: The order is NOT deleted

      Reply


    Would you like to share your thoughts?

    Your email address will not be published.

    Software development and outsourcing blog by QArea © 2016

    Яндекс.Метрика