An effective test strategy
- Should clearly be based on the input from the stakeholders,
- It should give directions to the tester in what to test, but give him/her the freedom to define tests on the basis of his/her test-, system- and domain-knowledge
- It should fit within an agile context,
In the 9th edition of my G(r)ood testing column I explain that many testers wonder how their test strategy will change if they move to agile. I’ll introduce a different approach for setting up an test strategy that meets the above criteria and might surely benfit you.
Watch the introduction video below or go to the column on the Eurostar community pages