What do you want to from today's session?
If you want to get more specific: what do you want to change about how you test?
Expectation vs Deliverable (two circles)
Purpose and Judgement
- Ways to grow your understanding of product risk
- Basics of exploration in testing – revealing risk vs verifying value
- Exercise to find surprising behaviours / qualities
- Using automation in exploration
... then questions, if you have them.
Understanding Product Risk
Product Risk Exercise (5 mins + debrief)
We'll make new groups around several of infi.nl's products. Join the group that best suits you (if we can't move ourselves to rooms, change your screen name to make the host's job easy).
In your groups, talk for 3 mins about how you've developed your understanding of product risk for that product. Put a sticky or two in the box when someone in your group has something to talk about.
Debrief: We'll come back into the big group and pick a few of the stories.
Raster Reveal Exercise (~3x1 min, debriefs)
1-minute exploration, short debrief, repeat
Explore the image: move over parts where you want to see more.
Then we'll talk about it. Some questions:
- When did you know what you were looking at?
- How did you know?
- Did you think it was one thing before revealing another?
- How could you describe your actions? Would your actions transfer to another person? Another picture?
- What role do your knowledge, skills and judgement play in exploring this?
You may want to go to converter's own page to use it more directly.
Priming Exercise (2 mins + debrief)
Check out the story, the examples, the tests, the release notes.
Try some values out by hand. Take a look at the basic / slider / numeric inputs – all these are browser-based, but can give you a swifter means of interaction.
Debrief question: what have you found out about the underlying system?
Judgement Exercise – in groups (5 mins + debrief)
Use the pre-filled list to see how several values are converted. Feel free to change those values.
- Do you see any surprises – reasons to change the model of the underlying system which you build in the previous exercise?
- Do you judge any of the outputs to be wrong? What are you basing that judgement on?
- How did you change this collection of tests? Why?
Targeting Exercise – in groups (3 mins + debrief)
Imagine you've been given the task of testing the underlying system. You'll skip the browser entirely. In groups of 3-6, consider one or two of the following questions.
- What's worth verifying?
- What's worth exploring?
- How might you automate the exploration part?
Debrief: put short answers on the miro board, we'll pick up from there.
Exploring with Data Exercise – in groups (up to 10 mins + debrief)
Use the list box (or the data generation tool) to try out several values at once. Examine your results, and try more data to dig into what you find.
The UI will get in your way: feel free to use an external tool to generate lots of data, and to look at your results. If you want a tool to generate, work with the 'generated bulk input' option.
As you work, put answers on the board to the following questions
- what data did you choose to generate first?
- what did you change in later tests?
Look back over your notes. Find the "conclusions" section on the board. Use stickies to share actions and insights. We'll pick out a few to elaborate.
Questions are the best bit. I'm happy to take any question, any time – I'll defer longer answers and conversations to the end. There's a space on the board for you put yours.
Our workshop is on Monday 24 March. We'll run (check this) 15:30-16:30 Dutch time, with questions until 5. We'll be on infi.nl's Zoom channel.
James is a tester. He's been testing since 1996, and teaching explorartory testing since 2001. He's won awards for his work in the testing community, and for his writing. In his day job, he's a test strategist and mentor.
LinkedIn: James Lyndsay