Scribd
Upload
29 views

User Testing Rules

The document provides guidance on properly writing bug reports with exemplary and non-exemplary examples. It stresses the importance of including what, where, and when details to clearly describe the bug without ambiguity. Titles, steps to reproduce, actual results, and expected results should be written to explain exactly what is happening rather than what is not happening.

Uploaded by

staarcorner
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
29 views

User Testing Rules

The document provides guidance on properly writing bug reports with exemplary and non-exemplary examples. It stresses the importance of including what, where, and when details to clearly describe the bug without ambiguity. Titles, steps to reproduce, actual results, and expected results should be written to explain exactly what is happening rather than what is not happening.

Uploaded by

staarcorner
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

USER TESTING RULES

Exemplary bug titles


Wrong: Error shown on the Cart page
Correct: An "Error 500" will be shown on the Cart page after the user clicks on the "Checkout"
button
Wrong: The user cannot add a product to the Cart
Correct: "Unexpected Error" was shown on PDP, when the user selected Size and clicked on the
"Add To Cart" button.
What is wrong with the examples above: there are many possible scenarios in which these
titles would fit because they are too abstract. The reader does not know what actions you perform
and how the system responds to them. Hence, the reviewer has to read through the whole report
to understand what the bug is and cannot distinguish this bug from others easily.

It should contain information: what is the bug, where did the bug happen, and when the bug is
triggered? So when you write a title for your bug report, always remember: What? Where?
When?
When you write a bug title, describe what is happening instead of what is not happening. Your
title should never state that something does not work, otherwise the reader has no idea what is
actually happening.

STEPS REPRODUCED
The first step must contain an indication to access the URL of the landing page
provided by the customer in the Access section if you test a website or an indication
to open the app (with its name) if you test a mobile app. All further steps should
describe your actions from the initial step up to the point when the bug occurs – what
buttons you press, what links you follow, and what you enter. Your last step must
describe the action that you perform that triggers the bug. Remember that "observing"
is not an action taken by the user.

Exemplary steps
1. Go to http://www.examplewebsite.com
2. Enter any search query in the top-right search bar (e.g. “San Francisco”)
3. Click on “Search Now” button
4. Scroll down and click on "Sort by"
5. Select the option "Sort by price: High to Low"
Exemplary BAD steps
1. http://www.examplewebsite.com
2. Observe
3. Search > Sort > High to low
4. Observe

ACTUAL RESULT

Exemplary actual result


Wrong: Error shown on the Cart page after clicking on the Checkout button.
Correct: When the user added some product to the Cart and tried to proceed to the Checkout
page, he will notice that he will be not able to do that. An "Error 500 - Internal Server Error -
Sorry, something went wrong" will be shown when the "Checkout" button is clicked in the right
side menu.

Wrong: The user cannot add a product to the Cart, an error is shown.
Correct: After the user opened "Test IO - Product 1" detail page, selected Size: 36, and clicked
on the "Add To Cart" button, he will experience an "Unexpected Error" error message banner in
the top right corner of the PDP, and the product is not added to the Cart.

EXPECTED RESULT

Exemplary expected result


Wrong: User can proceed to the Checkout
Correct: After adding some product to the Cart, and clicking on the "Checkout" button, the user
should be redirected correctly to the Checkout page, where he should be able to add shipping and
payment info and place an order.

Wrong: Product should be added successfully to the Cart.


Correct: When selecting Size: 36 for the "Test IO - Product 1", and clicking on the "Add To
Cart" button, the product should be added successfully to the Cart. The user should not encounter
any errors in this process.

You might also like