Approaching testing with curiosity, not just scripts help uncover deeper issues & aligns better with real-user scenarios.
Do you use this mindset in your workflow?
5W1H- What, Why, When, Where, Who &How
2 Likes
Following a script like an explicitly written ‘test-case’, or an ‘acceptance criteria’ or a ‘use-case’, generally questioning and looking for trouble is reduced to nothing.
Otherwise it’s/should be constantly going on.
At one point it can end up being detrimental if exaggerated, due to creating oneself so much uncertainty.
One can lose too much time on chasing un-reproduceable issues, or trying to find the whole model of the solution design and all the variations and gaps where one could find issues, or annoying people to the point they start avoiding or ignoring the person, or getting told what you should do and how (because it seems you don’t get it..), and so on.
1 Like
I thought it was the 5 Why’s 
Yes but not just before testing, probably more during 3amigo’s or refinements.
1 Like
Thanks for sharing your thoughts. I completely agree-the mindset o f ongoing question should not be restricted to test case execution alone, its more about cultivating curiosity throughout. Also, great point about balance.
haha, will ask new question for 5 Why’s 
Glad you brought that up it’s cool how different models spark different angles of thinking.
1 Like