IT Blog, Web Development,

The Right Scenario for Reporting a Bug in Repro Steps

2 m read
QArea Expert
QArea Expert Marketing Manager
August 19, 2013
Share on
Reading Time: 2 minutes

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.

Categories

Recent Posts

  • Best Frontend Programming Languages to Create Beautiful and Fast Interfaces

    Read more
  • Capability Maturity Model Integration – QArea's big journey

    Read more
  • QArea is a Unique Services Provider in 2019 CEE Awards

    Read more
  • Ultimate Development Trends in 2018 to Reward Your Business in 2019

    Read more
  • Why You Should Write Your Next Microservice Using Golang

    Read more
  • 7 Reasons to Truly Love Microservices

    Read more
  • The Best Languages for Microservices

    Read more
  • QArea's Year: Summing Up 2018

    Read more

Subscribe

Yes

Tags
Share on
Privacy Preference Center