LEVEL UP Your Reporting
Get ready to dig into this bug mystery! We’ll find out everything there is to know, from the title to the results and beyond. So, fasten your seatbelts and let’s get started!
Feature: | Product Detail Page. |
Bug Type: | High Functional Bug. |
Title: | There are no reviews on the ❝Franklin Pit Cover❞ product detail page after clicking on the ❝Reviews❞ product tab, although the page indicates that there should be 2 reviews. |
URL: | |
Steps: |
|
Actual result: | When the user clicks on the ❝Reviews❞ product tab on the ❝Franklin Pit Cover❞ product detail page, there are no reviews in the tab (and no error messages), although the user can see ❝2 reviews❞ under the product title. |
Expected result: | The user expects that if the PDP indicates 2 reviews, they can see and read them after clicking on the ❝Reviews❞ product tab. |
Rule of Thumb:
A bug report title should be descriptive, not instructional. Focus on describing the bug instead of what the user does on the website.
The title should not have information already collected by the bug form, like the feature selected, the testing device or the browser used. Unless the issue is only presented on one specific browser or if the customer requested to specify the OS/Browser combo in the title, like [Win10/Chrome].
The actual and expected results start with describing the problem encountered or the anticipated behaviour. Refrain from summarising the title or steps as they were previously mentioned.
Practical task for you:
Pick one of our #BugsExplained shorts and identify the seven sections above.
The more you practice, the better you'll get at bug reporting!