Introduction

There are different types of tools focused on the management of tasks, which allows us to have control of what we do, set time, generate analysis (add link).

When testing and finding a bug, it must be transmitted to the team so that it can act as soon as possible to solve it.

How to report bugs

These are the things you need to consider creating a bug

  1. Create a "bug" (new "ticket" where the bug is written) with the title that describes what happened.
  2. Choose the appropriate values for the indicators "In which version is it presented", "In which project", "Browser", etc.

Within the indicators, Severity and Priority are also defined.

Severity has to do with the impact of a defect occurring, while priority is given by the business and is related to the urgency of resolution

<aside> 💡 The priority is defined by the level of impact for the business. But the Tester must be trained to understand how and in what way it affects the business. In this way it is possible to define and guide the customer with a more exact precision of priority

</aside>

The description must be clear and understandable so that the person who is going to take it can reproduce it. From this you get the following:

Steps. This part describes the step by step to reproduce the bug.

Example.