I’m curious as well. I’ve heard reference to exploratory testing charters but haven’t seen them in use. Does anyone get value out of that? I’m leaning more toward testing activities delivering artifacts that the team can review and grow since product knowledge is easy to lose on a big enough system.
puzzles to show the team an example and encourage them to use it in their daily work ?
anyone tried those exercices with his team ?
I’m curious to know what they liked the most ? and what were their finding ?
Many thanks @simon_tomes for all the useful examples and videos he shared about exploratory testing !
I have a new question, can we combine different methods together ? or we can run different sessions with different focus every time ?
Teh plan I prepared :
I ask them to think about the mission (what’s the purpose of their testing)
Combining the value/risks/questions approach with the four steps you’ve described makes total sense. And I’ve found starting with the value/risks/questions approach before jumping into charters is an excellent way to come up with charters. Cos they end up anchoring to value and risks.
Sometimes the “questions” can just turn into charters when reworded and sometimes I’ve found the questions become questions to ask during a session.