Please enable JavaScript.
Coggle requires JavaScript to display documents.
Test planning workshop (Goals (Get people to think about what they are…
Test planning workshop
-
Exercises
TASK: Set the Question
I have a calculator, i dropped it, how can i test it works?
Ask attendees to spend some time considering this. They can discuss in their groups and ask the facilitators questions.
AIM : To demonstrate how we make assumptions and not asking questions leads us to doing things which aren't relevant
ANSWER : The 'calculator' is actually an abacus. Attendees will usually start generating test ideas straightaway eg .'can you turn it on'. Some may ask question like 'where did you drop it?' / what height from ?
If asked what kind of calculator you can just say 'a normal calculator'. To demonstrate ambiguity in requirements
A good answer from an attendee would be to ask you to describe the features / appearance of the calculator thoroughly before coming up with test ideas.
-
-
-
TASK : : Present attendees with a simple looking piece of code / workflow. (we have one we used in RST) What do i need to do to test it ? Attendees can ask questions.
ANSWER :
The code is from a satellite but attendees are not told this. This would obviously affect the kinds of testing which need to be done.
Rather than diving in and suggesting test ideas attendees should ask questions to establish the context first.
Knowing about the context can affect the types of tests that need to be done.
- Identifying risks and generating a plan
-
INTRO : idea of identifying risks as a way of creating a test plan and prioritising what needs to be tested
TASK : Use the model generated in the previous exercise and highlight what they think the main risks might be and add these to the model / map.
What testing could you do to mitigate these risks ?
Are there any tools you could use ?
ANSWER : We want to see attendees indicate where risks could be. They might also suggest ways to mitigate these, they could also suggest how else they might identify further risks - ie speaking to developers / product owners
- Modelling out the product
-
AIM - To get attendees used to modelling out the product being tested as a way of starting to work out what they need to test
TASK :
Introduce a small application - we can find something we can use, either a Windows app or something like Ticket Magpie
-
ANSWER ; We aren't assessing their drawing skills. We want to see they can clearly understand what they are testing and communicate this via either via a mindmap or other model type representation
Ideally they would also identify speaking to the developers / product owner about their interpretation of the product to make sure it is correct
-
- Are we building the right thing?
-
-
-
-
Goals
-
-
-
-
Demonstrate the point that diving in and testing isn't the best way to approach a task. Testers should be planning, though not necessarily creating a 'Plan' as an artifact
-
-
-
-
Discussion
-
Emphasis should not be around test plan format, but the activity of planning and collaborating with the wider team
Where do the team think automation could fit in? When could you start discussing this ? How could it affect your plan?