Breaking down a User Story into Scenarios or Examples for execution.
under review
Murali K
Why - A User Story is a one liner, and testing for this should be covered by number of Scenarios , combinations and examples like in BDD. So a User story can be confirmed as passed only if all the scenarios under it are passed.
What - For example a User Story - "As a site visitor, I can filter product listing by price range."
To ensure complete coverage and pass/ confirm this User story for a online store we need to execute multiple scenarios for multiple menu options like:
- User should be able to filter product listing by price for "Apparels"
- User should be able to filter product listing by price for "Footwear"
- User should be able to filter product listing by price for "Accessories"
- User should be able to filter product listing by price for "Men's Wear"
- User should be able to filter product listing by price for "Women's Wear"
- User should be able to filter product listing by price for "Kids Wear"
- User should be able to filter product listing by price for "Jewellery"
- User should be able to filter product listing by price for "Brands"
- User should be able to filter product listing by price for "Gadgets" and so on ...........
To confirm a User Story as Passed, all the scenarios and options available under the User Story should be executed and passed within a short span of time for execution.
Tetiana Yezerska
marked this post as
under review
AV-Master
Hi Murali K. Thank you for your suggestions.
In your case you don't need to check all PDLs. You can check 2-3 cases. In the case of crowd testing, different testers will check different PDLs and thus ensure coverage. If the client needs to check each PDL, then in such cases separate user stories are created for each product category.
Perhaps clarification should be given in our academy on exactly how to perform such userstories.