When it comes to Exploratory testing how do we organise it and ensure we’re discovering the right information? Fortunately, with the use of charters we can plan and prioritise exploratory testing and use them to help us focus our testing. In this activity we’ll learn how to build charters quickly based on risks we feel might impact our products.
This activity is designed to help you become more familiar with the link between risks and charters and how we can use charters to test for specific risks. We’ll also learn how to use identified risks to help us create a range of charters for exploratory testing.
For this challenge we would like you to:
- Download one of the attached User stories for this challenge
- Read through the User story and support information
- Start by writing down a series of risks that you feel could negatively impact the feature
- Once you’ve captured your risks, write out five to ten charters that you can use for running exploratory testing sessions
Consider using tools like RiskStorming to help you generate risks
Try different templates for creating charters such as:
My mission is to test to discover
Explore to discover
Look at to test for
Help one another out by sharing risks and charter templates in this Club thread