The 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.
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.
Our team is already hard at work trying to resolve this issue.
Please resubmit your information tomorrow.
We're terribly sorry.
Take a look at our super-informative Blog
Learn more about Services
Check out our Case Studies
The more we know, the more accurate our estimate!
+41 43 508 07 94
We’ll get back to you within one business day!