"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!
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.
Good Example 1
Good Example 2
As a user, I can register for an account using my email.
The registration process using the email [email protected] and password MasterYoda123# went without any blockers. I was able to enter the email and password in the respective fields. Upon clicking on the Register button, the confirmation message shows up to notify me that my account has been created.
I was able to click on the Register button in the Navigation Menu. When the registration modal opened, I was able to enter a valid email and password. Upon clicking on the Register button, I was prompted with a notification that the registration was successful.
Yes. I created an account using [email protected]
As a user, I can log in using the credentials used during the registration.
The login process was handled as expected. I was able to use the email [email protected] email and password LittleOwl123! to login into my account. After entering mentioned credentials and clicking the Login button, I was taken to the Homepage.
I clicked on the Login button in the header of the website and landed on the Login page. I was able to enter my login credentials ([email protected] / abc12345) and log in to the website. The login function works without any problems.
I was able to log in using my credentials.
As a registered user, I can add products to the Wishlist.
The process of registration for an account went well using the email [email protected] and password [email protected] After registration, I was able to navigate to the POP and PDP. On the PDP, click on the heart icon added products to the Wishlist. Upon visiting the Wishlist page I was able to validate that the product has been successfully added to the Wishlist.
I was able successfully to register an account, and after that, I went to "Test-Product" PDP. There I selected the size of the product and clicked on the "Heart" (AddToWishlist) button. After clicking, the product was successfully added to the cart and confirmation was shown to me.
Click on the heart icon added products to the Wishlist.
As a user, I can filter shoes using the size filter.
Navigating to the Shoes category using the Main Navigation Menu went without any issues. Selecting size 39 in the Shoe Size filter displayed only relevant results.
I have opened the "Summer Shoes" product overview page via Navigation. There I opened the Filters menu and selected size 42 under the "Shoe Size" filter. Filter was applied successfully and relevant products were shown to me.
I can filter shoes using a size filter.
As a user, I can sort products on the search results page using the Low to High sorting option.
The search process was successfully started by clicking on the Search field, adding the search keywords and pressing the Enter button on the keyboard. Relevant search results were displayed. Click on the sorting drop-down opened the list and I was able to sort products using the Low to High sorting option.
I searched for "Blue T-Shirt" products and the search results page was opened. There I clicked on the "Sort" dropdown menu and selected the "Sort by: Low to High" sorting options. After that, all products were displayed in the correct order.
Click on the Low to High sorts products accordingly.
As a logged-in user, I can proceed to the Checkout.
Logging in to my account using the email [email protected] and password TinkerBell123% was completed without any stoppers. I successfully added one of the featured products from the Homepage to the Cart. Using the Cart icon in the Navigation Menu, I navigated to the Cart and clicked on the Checkout button. The Billing section of the Checkout loaded without any issues.
I have logged in to my account and added a few products to the Cart. After that, I opened the Cart page and clicked on the "Continue to Checkout" button. After clicking, I was successfully redirected to the Checkout page and I did not experience any problems with redirection.
I can proceed to checkout.
As a user, I can remove products from the Cart.
After adding red Converse All-Star Snickers in the size 41 from the Wishlist to the Cart, I was able to navigate to the Cart using the Cart icon in the Navigation Menu. The Cart page loads without any glitches. Click on the Delete button removed the product from the Cart.
I have added "Test-Product-1" to the Cart and went to the Cart page. There I clicked on the "X" (Remove) button, next to the product price, and the product was successfully deleted from the cart. Also, and confirmation message was shown at the top of the page.
I can delete the product from the Cart.
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.
Good Example 1
Good Example 2
As a user, I can pass level 1 in the game.
Opening the game XYZ application prompts me with the new player tutorial on how to use the game for the first time. When the tutorial is completed, I tapped on the Start button. Level 1 interface loaded, all game elements were responsive, and I was able to shoot all the ducks in Level 1. The expected reward for passing Level 1 was missing at the end of the level.
I have opened the app and completed all tasks which are included for Level 1. But after completing the last task for Level 1, instead of loading Level 2, the app crashed. I am unable to pass Level 1.
The Level 1 reward is missing from my profile.
As a user, I can edit the Player's Profile Settings.
Tapping on the gear icon in the top right corner of the Game interface opens the Player Profile Settings. I could open the game difficulty, and audio settings, to change the Player screenname and avatar. Upon changes, I was notified about the server error.
After tapping on the "My profile" button/icon at the top left of the screen, and clicking on the "Edit" icon, nothing will happen. I am unable to open the Edit screen and change profile settings.
Server error present on Player's Profile Settings.
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.
Good Example 1
Good Example 2
As a user, I can subscribe to a Newsletter using a valid email address.
Upon scrolling the Homepage to Footer, I noticed that the Newsletter Subscription field is not located slightly above the Footer the way it was stated in the feature description. Further inspection of the website proved that the feature is either hidden for some reason or not implemented yet.
After opening the Homepage, only a blank(white) page was shown to me. The website is not loaded so because of that I am blocked from testing this User Story.
The Newsletter feature is not there.
As a user, I can find a nearby store using the Store Locator.
An attempt to open the Store Locator using the link in the Navigation Menu triggers endless loading. Store Locator Page fails to load within 2 minutes. Having known that this is the only option to test the selected feature, I can't proceed further.
When I opened the homepage I did not find any Store Locator icon or link on the website. After taking a deep look at the website, I found out that Store Locator is still not implemented yet, so I am blocked from testing this user story.
The page loads endlessly.
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.
Related articles and links