"Executing User Story doesn't require any mastery." WRONG!
You can and you should improve your User Story executions from one test cycle to another. Constantly!
Motivation
Executing User Stories has become very popular among our tester crowd, and we are delighted about it. Increasing the % of executed User Stories per test cycle makes everyone happy:
testers increase their income.
Test IO makes sure that the customer is happy.
customer is ensuring that the happy path in the normal user flow is spotless.
The details on how to execute User Stories can be found here.
What is the difference between good and bad User Story Execution?
There is no precise formula but there are some examples we could share with you to distinguish if the text you provided in the How did you test field is useful for the customer or not.
In the table below, you will find some positive and some negative examples of the same User Stories with the status Yes. We offer you 2 good examples for each User Story. Please, use them as a reference and compose your own How did you test part of the User Story.
Remember: The features in 2 test cycles can have the same User Stories but how the products are designed will determine which steps you mention in the How did you test field.
For instance, 2 different websites have the option to register for an account, but it doesn't mean that both will display the confirmation message at the end of the registration process nor that you will be presented with a tickbox to select "I agree with terms and conditions of this website" before you click on the Register button.
User Story | Good Example 1 | Good Example 2 | Bad Example |
As a logged-in user, I can proceed to the Checkout. | I clicked on the Checkout button in the Cart, and the Checkout page was shown. | n/a (if the screencast shows the execution fully) | I opened PDP and added product to the Cart, then I proceeded to the Cart and saw that the product is placed in the cart, and I clicked on the Checkout button, which redirected me to checkout. So, I am able to proceed to the checkout without any issues. |
As a user, I can filter shoes using the size filter. | After applying Size 42 relevant products were shown to me. | n/a (if the screencast shows the execution fully) | I can filter shoes using a size filter. |
As a user when I encounter a PDP the PDP will have a price or “sale” listed under its name fallowed by its shipping information (if shipping information is available). NOTE: a listing Contains multiple PDPs and as such it will not show price or sale. Be sure the page is a PDP not a “listing”. | On the PDP for ABC product, I was able to see the price and shipping info. | n/a (if the screencast shows the execution fully) | As a user, when I opened different PDPs, the PDP had a price or “sale” listed under its name followed by its shipping information if shipping information was available for that product. |
Given: I am a logged in user When: I click on the heart logo in the bottom right of the PDP main image | On PDP when I tap on heart the item was successfully added to the saved items followed by confirmation message and heart was filled red. | n/a (if the screencast shows the execution fully) | The User Story is working, I can add a product. |
After scrolling to the last video/image, there should be two buttons. One takes us to the top of the screen. The second one takes us back to the Streams screen. The last video/image here means the very last one after all posts loaded, because after scrolling there is new posts that will appear each time and not the buttons. | After I tapped on the first button, I was redirected to the top, and after I tapped on the second one, I was redirected back to the corresponding screen. | n/a (if the screencast shows the execution fully) | Both functions work as expected. |
The following table will cover the positive and negative examples of User Stories with status No. Do your best to understand the difference and apply the learned logic to your future User Story executions.
User Story | Good Example 1 | Good Example 2 | Bad Example |
Given: I am a not logged in user When: hover over a non saved item Then: I a see a hover state message that says “Click to save” And When: I click the heart or hover state Then i am redirected to a login page and Then: after i log in I will need to tap the heart again to save/favorite it and fills in and a new message is displayed “added to your saved items” with a hyperlink that can take you to your saved items. | When I clicked on “heart”, no reaction and redirection did occur, I remained on the same page, and the login page was not opened. | When I click on the “heart” button, I was redirected to an Error 404 – Page not found. The login page did not open. | The login page did not open. |
As a user, I can edit the Player's Profile Settings. | Clicking on Edit button in profile settings will trigger an Error page – Error: 500 Internal Server Error. | After clicking on the „pencil“ (edit) icon on the Profile Settings page, no reaction will occur – “edit” screen was not shown. | I can't open Edit, no reaction on it. |
The last table will equip you with the knowledge of how good and bad examples of User Story with the status Not possible to test look like. Make sure that you understand the difference and apply the gained knowledge in future User Story executions.
User Story | Good Example 1 | Good Example 2 | Bad Example |
As a user, I can subscribe to a Newsletter using a valid email address. | The newsletter function was not presented on the website. I also tried to navigate through the website, but did not found the newsletter function. | I tried to open the website, but only a blank page was shown. The website was not opened, even in a few different browsers. | There is no newsletter. |
As a user, I can find a nearby store using the Store Locator. | There was no Store Locator option presented on the Website. Different parts of the website were checked, such as the header, the navigation, the footer, the detail pages, but the store locator was not presented. | The Store Locator page showed „Construction in progress – Store Locator will be released soon“, so the function was still not released in time of testing. | I can't find Store Locator on the website. |
Once you finish comparing the provided positive and negative examples, you will for sure already have an idea of where you made the mistake the most and how can you improve your User Story executions in the next test cycle you take.
Remember: Good testing practice takes time and willingness to learn from one test cycle to another. Improving your User Story executions will make you feel good and trust us... there is no better feeling than knowing that your User Stories have been accepted with a 100% success rate.