ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
TitleStepsActual ResultExpected ResultSeverityCommentKeywords
2
Filter with checkbox / selection (e.g. for color / size) shows the irrelevant items.1. Land on a Category or a Product Overview page.
2. Filter with a checkbox / selection for color / size (e.g. color red / size L).		Besides the correct products, some wrong products are shown.Only the filtered products are shown.ContentFor checkbox or a selection (e.g. size / color), not a range (e.g. price range):
--> The filters work and show the product based on its defined tag / specification, if wrong product is shown
=> Content (wrong tagging from the Admin side), technically, the function is still working.

**Note**
If it's a range (e.g. price / length range)
--> The filters recheck & show all the products among the ranges. If wrong product is shown
=> High functional bug.		filter, color, size
3
Applied filter / sorting is reset after going back to the Products page.1. Apply a filter / sorting on the Products (Overview / Category) page.
2. Go to the detail page of any product.
3. Go back.		The applied filter / sorting is reset after going back.The applied filter / sorting must be kept.LowAfter going back, if the URL is containing the filter / sorting parameters but they are still reset then it's a Low bug as the users can easily re-apply them.

**Note**
If the URL does not contain any filter / sorting parameters then it's NOT a bug when the page is reloaded with the initial values after going back.		filter, sort, back
4
Validation for an invalid input is implemented but for a similar invalid input, it's accepted.1. Land on a form (e.g. Registration).
2. Input an invalid email address, e.g. 'abc..def@xyz.de'
3. Input another similar invalid email address, e.g. 'abc.def@xyz..de'		The validation is shown for case 1 but for the case 2, with a similar invalid input, it's not shown.As the validation is already implemented, all the similar invalid inputs should be validated.LowValidation is already implemented by the Customer but it's not working effectively in all the cases.

**Note**
- We have different validation types, having the validation for "cannot be empty", does not mean it will also validate for "cannot be a special char".
- Without proving the validation is already implemented (as the example), then missing the validation for a specific input is a Usability Suggestion instead.		form, validation
5
Dead / wrong links on the main navigation elements (header / footer / breadcrumb).1. Try to open a link at the Header / Footer / Breadcrumb section of the web / app.Redirected to Page Not Found error page or an irrelevant page.Redirected to a correct / relevant page.LowEven if corresponding links can be defined in principle within Content Management Systems, they are often assigned to the more static parts of a website and are therefore not directly regarded as content.

**Note**
- It'll be upgraded to a Low bug when it occurs on the header / footer / breadcrumb.
- If it occurs on page's body, it'll be assessed as a pure Content issue and will only be upgraded if it affects the functions.		dead, wrong links
6
After logging-out & going back, the Personal Data are still visible or can be changed. 1. Login & land on the Profile page with private data.
2. Logout.
3. Use the (browser's) back button.		Personal data is displayed / can be altered although you are not logged in anymore.A login form / the main page or some info message about being logged out is shown.HighPrivate data (that are protected via a login mechanism) have to be protected and should not be accessible after logout.form, back
7
Basket/Cart data are lost after logging in again.1. Login > Add some products to Cart.
2. Logout & login again.		The products in the Cart are lost.The products in the Cart are still kept.HighHigh bug as the users can still add the products to Cart again.

**Note**
Sometimes, the Cart data are stored on the browser / sessionID which is technically cleared right after logging-out.
To make sure that it's a valid bug, we must prove that:
- The Cart data are stored on the account database (by adding the product to Cart & login on another browser to recheck). 		shopping cart
8
Social Login - The previously logged-in account is auto chosen again without showing the account list to the users.1. Land on a Registration / Login page.
2. Select a Social Login method (e.g. Google).
3. When the Google's account list is shown, select an account to login.
4. Logout & attempt to login with same method again.		The Google's account list is not shown anymore, user is directly logged-in with the previoulsy chosen account.The account list must be shown to let the users choose which account should be used.Not a bugThis is the standard behavior. After also logging out from Facebook / Google, another login prompt will be shown.social login
9
Search with a keyword that contains special characters: Returns "No result" or other unwanted behaviors.
1. Find a product which contains special character on their name.
2. Search with a keyword that contains special character (e.g. an apostrophe, a comma or a colon)		Returns either "No Results" or any other unwanted behaviors.The relevant product can be found.LowIf the keyword is relevant to an existing product:
-> Low bug as it's relevant to some special products only, the Search feature is still working generally.

**Note**
If the keyword is totally abnormal / not relevant:
-> Not a valid bug.		search, special character
10
Search suggestion is also closed after closing the keyboard.1. Land on a Search field, type some keyword.
2. When the suggestions are shown, close the keyboard.		The suggestion popup is also closed after closing the keyboard.After closing the keyboard, the suggestion popup should be still there.UsabilityTypically, the search suggestion is clicked during the input process. Providing the functionality even after closing the keyboard is more like an additional comfort for the user.

**Note**
It's a Low bug when:
- Keyboard covers the suggestion popup, users try to close the keyboard to see all the suggestions but then, suggestions will also be closed.		search, suggestion, close
11
Search suggestion is not shown after pasting the search keyword.1. Open the site
2. Click on the Search field
3. Paste search query 		Search suggestions are not shown after pasting text. Search suggestions are shown after pasting text.LowThis would be a low functional bug. Search suggestions are shown on keyboard event.copy & paste, search
12
Searching with a combined keyword (e.g. black & white) and switching the order leads to different results1. Do a search for a keyword contain more than 1 word (e.g. black & white)
2. Search again with a different order of the keywords (e.g. white & black)
3. Compare the results between them.		Different results are shown although the users just swapped the keyword's content (e.g. "black & white" and "white & black").

Both searches deliver the same search resultsNot a bugThis is not a bug. searches are not always done by a simple string comparison. Nowadays it often uses vectorization and other techniques to perform fast in a huge amount of data. As so a different string results in different results by purpose. It often also puts a priority on some in the string. Common behavior also in all big players search algorithm.search, keywords, results differ
13
Submit the form with empty or invalid fields: Unclear error message (ex: The form cannot be submitted or An error occurred) appears.1. Fill in a form with wrong data or let fields empty
2. Submit the form		The unclear error message (ex: The form cannot be submitted or An error occurred) appears without specifying exactly what the error is / which field is wrong.A precise message to highlight / mention the error fields should be shown.UsabilityMake a more precise message what happen is UX. It is right now not implemented and most likely use a catch all and show the general error. validation, error message, form filling, form submitting
14
After moving to the next field (e.g. by using keyboard's next button), the cursor is placed at the beginning, not the end.1. Land on a form (e.g. Registration).
2. Fills the First Name & Last Name.
3. Focus on the First Name field & press on the Next button on keyboard (or directly tapping on the Last Name field).		Cursor is placed at the beginning of the field.Cursor is placed at the end of the field.Not a bugIt's not a bug when the cursor is shown either at the begining or the end but a design choice. The users can start their edit from the first char or the last char on field, so, it's also not a UX.cursor
15
Placeholder text is cutoff as the field is too small.1. Land on a form (e.g. Registration).
2. Review the placeholder text of all fields on the form.		The placeholder text for some field is NOT visible fully (e.g. "Enter your address here" is shown as "Enter your add")The placeholder text is visible fully OR
correctly abbreviated with 3 dots at the end (e.g. "Enter your address...").		VisualThe field should have an appropriate size or other means should be in place to provide a visually appealing user interface.form, truncation, placeholder
16
After opening a form, cursor is auto placed on the 1st field but keyboard is not shown.1. Land on a form (e.g. Registration).
2. Review the cursor at the 1st field.		Cursor is blinking on the field but keyboard is NOT shown, it's only show after tapping on the field.Keyboard is opened.Not a bugThe cursor is blinking to attract the user's attention, it's not a bug but a design choice when the keyboard is not auto shown without user's intention.cursor, keyboard
17
Deactivate next step/submit button until all fields are filled with valid inputs1. Land on a form (e.g. Registration).
2. Do not input any field or input some fields (not all).		The submit button is still enabled. Validation will be shown after pressing.The submit button should be disabled until all fields are filled with valid inputs (according to the implemented validation rules).Not a bugThis is not a meaningful usability suggestion as there are a number of aspects that are not / cannot be addressed, e.g. when to mark a required, but yet empty field as missing.form, validation
18
Space is counted as a valid character.1. Land on a form (e.g. Registration).
2. Try to input only spaces for a field (e.g. Name).		The input for the mandatory field is accepted as 'valid'.The entered value is not considered a valid input for a mandatory field.Not a bugTechnically, space is accepted as a valid character & normally, for a required field, only "not empty" validation is implemented.
Missing a validation for space is also not a valid UX since it's not an end-user's normal behavior.		form, validation
19
Show Password icon - After tapping on it, keyboard is auto closed.1. Land on a Registration / Login form.
2. Type the password then press on the Eye icon to reveal it.		Keyboard is closed after tapping "show password" icon. Keyboard is still shown after tapping "show password" icon and password is revealed. UsabilityWhen pressing on the Eye icon, the cursor won't be focused on the field anymore, as a result, the keyboard must be closed.
This is a Usability Suggestion to maintain the cursor on field.		password
20
When password is hidden / masked, move out & re-focus on the field, after typing, the password is cleared.1. Land on a Registration / Login form.
2. Type the password.
3. Move out of the field & re-focus on it to trigger the keyboard again, continue to type the password.		Password is deleted. New character is added/deleted on encrypted password.Not a bugWhen the password is masked, for the security reasons, if the users move out & re-focus on the field then start typing, some Customer will intend to clear the password to force the users input again so that they can ensure that the true owner is using the app.

**Note**
When the password is revealed (unmasked), if it is still cleared then it will be a Low bug.		password
21
No action is trigerred after tapping Go/Return/Enter button from keyboard 1. Land on a form (e.g. Registration).
2. Fill some fields.
3. Press on the Go / Return / Enter button from the keyboard.		No reaction. Form is not submitted or keyboard is not auto closed.A corresponding action (submit the form or close the keyboard, etc.) must be done.UsabilityThis is a usability suggestion to assign additional actions to keyboard button.keyboard
22
Copyright year is not updated to the current year 1. Open the site and scroll to the footer
2. Pay attention Copyright year is not updated to the current one 		Copyright year is not updated to the current year Copyright year is updated to the current year Not a bugThis is not a bug. Copyright year depends on when site content was added and updated. footer, copyright year
23
The old value (before editing) is still shown after using Back button & only shown correctly after reloading.1. Add a product to the Cart.
2. On the Cart page, delete that product.
3. (Optional) Go to another page.
4. Press on the Back button (from the browser or device).		The old value (deleted Cart's item) is shown again.
The correct value is only shown after refreshing the page (or go out & re-access the page to force the refresh).		The values on page must be always shown as the latest ones.Not a bugNot a functional bug but either a result from the browser's caching (web) or the app is not implemented to auto refresh after making changes & going back.

It's only a bug after refreshing the page, the old value is still shown.		cart, back, deleted, old
24
The background page can be scrolled while a menu / popup is being opened.1. Open a menu / popup.
2. Scroll over it.		You can scroll the page in the background (while scrolling the menu itself works fine as well).The page in the background cannot be scrolled as long as the menu is open.Not a bugAs there are no negative consequences, this is not a functional issue. As there is no impact on the user's workflow w.r.t. completing his/her task, this is not a usability suggestion either.scrolling
25
The opening object (dropdown / list / popup) is auto closed after rotating the device.1. Open some dropdown / list / popup / etc.
2. Rotate the device (ex: from portrait to landscape mode).		The previously opened object is auto closed.The object should be still opened.Not a bugIt's the browser's responsibility to handle layout change after device rotation. Not a bug of the tested site.
For the app, it's even by intentional when the page is auto reloaded due to new layout.		drop-down list, rotate
26
Cancel the action for some process (ex: PayPal payment or Social login): Unclear error message (ex: Something went wrong) appears.1. Trigger some popup (e.g. PayPal payment or Social login).
2. Press on the Cancel button on the popup.		The unclear error message (ex: Something went wrong) appears after cancelling the process.A more friendly message should be shown.UsabilityThis is not a functional bug. This would be rather a usability suggestion to add more clear message. cancel, error
27
[Mobile] Landscape mode - Keyboard covers most of screen's area & objects cannot be used even after scrolling.1. Open the site
2. Tap e.g. the Search field
3. Change device to the landscape mode
4. Try to scroll down, access some field, etc. 		Cannot scroll the page in the landscape mode. Can scroll the page in the landscape mode. Not a bugThis is not a bug. Screen height is too small in the landscape mode so device keyboard covers almost all of the screen. This is how device keyboard is designed in iOS/android. Developers of a website have no control over this.landscape, keyboard
28
Displayed discount and calculated discount differ for a product1. Find a product which is on promotion (discount, sale) which have a % badge on it
2. Calculate the % and compare with the badge / discount information		The price of product differs from the calculated price with discount.

e.g. 99,95$, tag say 50% off, but the item reduced cost 49,95$, which is not exactly 50%		The shown price after sale / promotion / discount matches the badge / information % for the discountNot a bugThis is not a bug. This is most likely done on purpose. Prices often uses psychology in the making, as so often we will have "beautiful" prices which promoted our brain to be good / cheap to convince the customer to buy. Those often ending on xx.49, xx.95, xx.98, xx.99 and so on. This is often wanted. To still have nice numbers it will not show broken percentages like 49,765%. Also keep in mind, this applies vice versa to the % to the set number too.promotion, sale, percentage, %, price, discount
29
After trying to access a 3rd-party payment gateway (e.g. Klarna), a blank or error page is shown (working fine with VPN).1. Open the website
2. Add a product to the Cart and proceed to Checkout.
3. Try to complete the purchase via a 3rd-party payment method (e.g. Klarna).		A blank page or error page occurs which prevents the users from completing the order.

---
If connecting the US VPN, the issue does not occur.		The users can complete the order normally on the 3rd-party payment gateway.Not a bugSome 3rd-party payment sevices (e.g. Klarna) directly confirmed on our legal Terms & Policies that they intentionally block the access from some specific countries.

So, to make sure that this is a valid bug from the Customer's product, please reproduce the steps with a US (or CA) VPN and only report the bugs if the issue persists.		payment, order, blank
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100