Thinking about Huib Schoot’s TestBash Detroit training The Magic of Sherlock Holmes: Test Strategy In The Blink Of An Eye! - made me think about what is the one thing you consider when building your test strategy. So I asked on Twitter and LinkedIn and got some great answers:
What problems we are solving? Why we are solving? How we are solving? Communication is the key so important people understand.
Long term reusability of the test suite and time for exploratory testing.
Risk, team capacity, team skillset, testers domain knowledge and technical skills and finally timeline and other concurrent projects if exist.
A clearly defined goal, regularly reviewed to focus all the teams actions and energy to fulfill.
It’s easy to say customer flows, and it is vital (after all, who else are we building for) but as time goes on? I’d say keeping the performance in check is absolutely essential.
Flexibility, collaboration and innovation. Customise your strategy. Throw away the rulebook and mindmap your unknowns. Be prepared to shift your original mindset.
exit criteria - otherwise when do we know we are finished
What would you add to the list? What do you consider when planning your test strategy?