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 Overview Page. |
Bug Type: | Content Bug. |
Title: | ❝Marvel Deadpool Bathrobe❞ displayed after visiting ELECTRICALS & TECH category |
URL: | |
Steps: |
|
Actual result: | The unrelated ❝Marvel Deadpool Bathrobe❞ product is found on the page. An item that doesn't belong to the ELECTRICALS & TECH products. |
Expected result: | Only products related to Electrical and Technology should be displayed in the ELECTRICALS & TECH category. There should be no irrelevant product listed on the page. |
This is a reminder that content bugs must be documented with screenshots. Here is the one related to this bug for your reference.
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:
Pick one of our #BugsExplained shorts and identify the seven sections above.
The more you practice, the better you'll get at bug reporting!