LEVEL UP Your Reporting
Check the combination of filter and sorting function
Here, navigate to the video for better quality.
Feature: | Product category page |
Bug Type: | High Functional Bug |
Title: | The applied price filter is reset to default on the "Boots" product category page after sorting the products |
URL: | |
Steps: |
|
Actual result: | Previously applied price filter (e.g.: from 685 € to 1290 €) is always reset to default (from 160 € to 1290 €) on the "Boots" product category page after changing the sort option for any other |
Expected result: | Only ❝Sold out❞ products are displayed on the ❝T-Shirts❞ product overview page after applying the ❝Out of stock❞ filter from the ❝Availability❞ filter section. In-stock products aren't presented. |
Useful tooltips:
When documenting bugs in a bug report, it's essential to enclose the names of elements such as buttons, links, fields, etc., within quotation marks. This practice ensures clarity and precision in communication, especially when referring to specific interface components. For instance, instead of stating "Click Submit button", it's preferable to write Click the "Submit" button. By enclosing element names in quotes, you distinctly identify them within the context of the report, aiding developers in understanding and addressing the reported issue accurately.
Learning the correct names of elements:
Site Logo: A graphic or text image displayed at the top of a web page. Clicking on it often returns the user to the homepage.
Search Bar: A visual element that allows users to search for specific objects, pages, or information on the website.
Navigation Menu: A list or set of links, typically located at the top of a web page, that allows users to navigate to different pages or sections of the site.
Language Switcher Menu: A dropdown or static menu that allows users to change the language of the website content.
Flyout Menu: A dynamic navigation menu that appears when hovering or clicking on a designated item, providing additional navigation options or content.
Common mistakes:
Here are some common mistakes that can occur in bug report steps:
Incomplete or wrong steps: Steps should be clear and complete so that another user can accurately reproduce the issue. It's important to include all actions that led to the bug.
Unclear step descriptions: Steps should be described clearly and concisely so that other users can follow the instructions accurately.
Lack of additional information: Sometimes additional information or context is required to reproduce the issue. For example, mentioning user data or other details that may be useful for developers.
Steps containing "Observe" or "Check": Steps should not contain results and explanations, only commands/actions.
All steps should start with a capital letter: To improve readability and understanding of the bug report, it's important for each step to begin with a capital letter.
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!