#3 Greenhorn 💚 Newsletter

Featuring julia.mashkowski, ecanor & mangaiv.pdv, a content bug, usually mistaken for functional and much more!

Charlie avatar
Written by Charlie
Updated over a week ago

Good example #1: Relevant steps

A good bug report follows our rules, provides all necessary information to identify the issue, and anyone who reads it can reproduce the behaviour without reading the entire report.

For instance, in websites like ASOS or Hugo Boss with a landing page and two shops to navigate to, WOMEN and MEN, lefting out which of these shops the user has entered is an enormous mistake since some bugs can only be found in a specific shop.

In the following report, you can see that every section is perfectly filled out and that all steps needed are mentioned, including the shop tested.

Good job, julia.mashkowski!

Notice that the severity for sorting issues is always high as per our Bug Severity Assessments spreadsheet row 8 because ❝As sorting is only a convenience function and the products can also be found via other ways, High is appropriate here.❞; so stay in the lookout for bugs on this functionality!

On the other hand, it’s always worth it to invest enough time documenting bug reports so Team Leaders and customers can like them, which gives you an extra 2€.

Good example #2: Excellent screencast execution

The following execution of a critical bug found on IMDb shows clearly, in every click, that the registration button is not displayed after changing the name in the Apple-ID modal window to Sing in with Apple.

Good job, ecanor!

You can find more tips to make your screencast shine in our article: Screencasts, section ❝Best practices while capturing a screencast❞.

Good example #2: Excellent report

As mentioned above, meeting our basic requirements for bug reporting is enough to forward to customers; however, if you want to stand out and thrive as a tester on our platform, the extra mile is the way to go!

Good job, mangaiv.pdv!

In this report, the behaviour is not only adequately explained; the workaround users need to progress over is also provided.

Common Mistakes #1: Filtering bug submitted as functional

One of the most common mistakes with filtering products is considering that a wrong result is a functional issue, especially with options like colour.

Colour filtering and similar filtering options are content bugs. This case can be found as the first example in our Bug Severity Assessments spreadsheet: ❝There is no underlying functional issue here, but the tagging of products (in the backend) is incorrect. This is not necessarily visible on the product detail page if the tagging is not explicitly presented to the customer.

The only exception we can think of when a filtering option presents a functional issue is with the price filter.

In this case, the feature needs to compare items with the set price range via code. If the items are not correctly displayed, the most likely reason is a functional bug.

Since this issue is not preventing users from finding items or purchasing them, low severity is appropriate.

Did this answer your question?