This challenge is one of the Exploratory testing week challenges that get you thinking about and practising Exploratory testing. Our challenges offer activities for you to learn new skills and knowledge as well as practise Exploratory testing. Whether you are just starting out in Exploratory testing or looking to try out something new. We have the challenge for you.
Introduction
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.
Purpose
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.
Activity
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
Some tips:
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
All we need is up to 30 minutes of your time for a demo of your solution and a chat with our host, answering questions on what you learnt. Not only will you help your peers within the community, but we’ll pay you £100 for your time! We will be focusing on this challenge on Tuesday, the 27th of April, from 5:00 pm (UK Time), so you will need to be available around this time.
So just like Challenge 1, I completed this challenge using MetroRetro. I started out by doing some risk storming using my TestSphere deck, identifying Quality Aspects which I thought were most important and could create some interesting exploratory testing ideas. I used these quality aspects to create a new template in metro retro and added post-its. I also used my TestSphere deck to come up with some ideas on how to test, and added these to the metro board. I also added some questions, things that we might want to check for in an exploratory testing session.
I didn’t base this on a specific platform, but I did have a hotel room booking form in mind (a little like the RestfulBooker platform)
Here is a link to the metro board so you can see some of the risks and ideas I identified. Please feel free to add some of your own. MetroRetro
Great questions! Thank you for passing them along @heather_reid !
@shalinigt : I usually go with 5 aspects. Configuration, Functionality, Performance, Security, and Accounting. These would typically cover all the aspects that need to be tested. Under each of the categories, I try to come up with risks based on what I see as missing in the scenarios, and what’s important for the end-user.
@bpennell : I prioritize the risks based on what’s important to the end-user. Discussions with the customer with the Product Owner / Representative engaged about the risks will help prioritize the risks.
Monika S: We can draft the charters as soon as you have the scenarios identified and the risks identified. These artifacts can be shared with all stakeholders for discussions. There will typically be an owner for the artifact, who will make the edits, but anyone can go through, comment, give feedback, and suggest improvements.
Hope that helps! Glad to answer if there’s more!