Skip to main content

Investigation of failure

Set defect type​

ReportPortal provides the possibility for test failure analysis of your runs. The investigation includes setting the appropriate defect type of failed items, posting a defect for them or linking the ID of a defect that is already created in the bug tracking system.

Using “Make decision” modal, you can choose the real reason of your failure and provide a comment for this fail.

When a defect is found in a test, the bug triage should be performed and proper defect type should be assigned to it, in order to have accurate test runs statistics. You will be able to change a defect type for a test and mark it as a Product Bug/Automation Bug/System Issue/No Defect at any time.

The available defect types are described below:

“To investigate” means that no investigation has been made on this defect yet.

“Product bug” means that the defect was investigated and a production bug found as the reason for the failure of this test.

“Automation bug” means that the defect was investigated and the automation test is not correct.

“System issue” means that the defect was investigated and it turns out that a system-level issue, like an app crash, caused the test to fail.

“No defect” means that the defect was investigated and was defined to be not a defect.

You can successfully work with basic defect types, or you can also create up to 70 custom defect types. Moreover, it is possible to have all custom groups of issues under 1 default defect type (if needed).

How to create a custom defect type?​

  1. Open Project Settings
  2. Navigate to “Defect Types” tab
  3. Click “Create Defect Type” button at the top of the page or click the icon near the defect type group
  4. Select the Defect Type Group
  5. Fill the “Defect Type Name” and the “Abbreviation” fields
  6. Select a color in the “Color of Defect” section (you can select any color from the color picker)

Thanks to custom defect types, you can get the following benefits:

  1. More specific defect types to identify the most problematic product area
  2. The ability to prioritize bugs based on more specific types of defects
  3. A possibility to assign people / teams

For example, there can be following custom defect types that are created on the project:

Product Bug Group – Billing feature, Backend bug, UI issue, Not implemented feature

Automation Bug Group – Test data issue, Timeout issue

System Issue Group – Permission issue, Environment issue

No Defect Group – New feature, Manually passed, Fixed (if the bug is fixed, but auto tests are not fixed yet)

note

There is also To Investigate Group for the defects that have not been sorted out yet.

important

A small life hack: you can identify defects by the name of the team and, in doing so, assign them to the appropriate team. This method can be applied within any defect type group.

Post bug to Bug Tracking System​

ReportPortal allows to connect some popular bug tracking systems with our test automation reporting platform and post a bug to them or link the ticket ID of the already posted defect to the test item in ReportPortal.

Before posting/linking a bug, make sure that the bug tracking systems are connected to the project on the project settings page. To check it, please, find the user guides below: