Tutorial : how to write a perfect bug report — 6 Chapters to get it all
You have been a lot to ask about this tutorial and we’ve thought you were right! In this tutorial we will help you be more efficient when reporting your bugs on WE ARE TESTERS, by explaining what we expect from you and what are mission manager will check when you submit a bug report.
Bug report form
In order to have similar bug reports among our testers in terms of structure and provided information, we’ve decided to have a precise template. It also help you identify the information you need to provide.
It looks like this :
In the following chapters, we will help you optimise the way you fill in this template.
The summary of the bug report is the first piece of information the customer (and in between the mission manager) will see regarding your bug. It is very important (read more…)
Chapter 2 : Actual Results/Expected Results
On WE ARE TESTERS, actual and expected results are the sections where you describe the bug you’ve experienced and what the normal behaviour of the bug is. Let’s be honest, most of the time (read more…)
Any brilliant QA superhero should have the ability to choose the right categories to classify his bug report (read more…)
Chapter 4 : Steps to reproduce
In the steps to reproduce the bug, you provide the path the customer and the developer have to take to see the bug you (read more…)
Chapter 5 : Device impacted
(work in progress)
Chapter 6 : Attachments
(work in progress)
Read also : 9 tools to become an efficient QA superhero
