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!
Here, navigate to the video for better quality.
Feature: | Search. |
Bug Type: | High Functional Bug. |
Title: | A blank page is occurred on the ❝Car leasing❞ search results page after trying to remove applied price filter by clicking the ❝X❞ button |
URL: | |
Steps: |
|
Actual result: | The blank page is displayed after attempting to remove the applied price filter by clicking the ❝X❞ button from the ❝Car Leasing❞ search results page. However, the price filter isn't deleted and still shown as applied on the ❝Car Leasing❞ search results page after refreshing the page. |
Expected result: |
Blank page isn't appeared, and applied filter is deleted on the ❝Car leasing❞ search results page after removing applied price filter by clicking the ❝X❞ button. |
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.
Learning the correct names of elements:
Product Tabs on the Product Detail Page are interactive sections typically found on e-commerce websites or platforms that display detailed information about a specific product. These tabs are organized into categories, with each tab focusing on a specific aspect of the product, such as description, specifications, reviews, or related products. Users can navigate between tabs to access different types of information about the product, facilitating a comprehensive understanding before making a purchase decision.
Common mistakes:
Utilize precise wording in bug reports. Phrases like 'incorrect,' 'does not work,' etc., do not accurately describe the issue.
Examples:
Wrong: The incorrect page is displayed after clicking “RedMi Note 5 Quick” article from “Support” search results page
Correct: Page with error 404 message is opened after clicking “RedMi Note 5 Quicл” article from “Support” search results page
Wrong: The “Service” link does not work on the “Company” page
Correct: Page with error 404 message is opened after clicking the “Service” link on the “Company” page
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!