The debate on test plan vs. test strategy has existed ever since testing became an important part of software project deliveries. So here is the most succinct yet humorous analogy you’ll find to help clear this up once and for all.
The aim of the Test Strategy is to direct the software testing processes of an organisation to support in the fulfilment of the organisation’s long term business objectives.The test strategy is the Mother of the test plan and thus guides and influences what the test plan contains.
The Test Plan directs the way in which testing is conducted for a particular software project. The test plan being the Child of the test strategy inherits the characteristics of the test strategy thus the many test plans that may be derived from a single test strategy will share mostly common traits. As with any child, the test plan also inherits certain characteristics from it’s Father who is different for every project. (no disrespect to Ms Test Strategy intended ;)
The question of the day then is “Who’s the Daddy?” The answer to that one is – The Project Plan – which lays out the specific needs defined by it’s associated project.
So the test strategy meets a new project plan, then after a few “meetings”, a new test plan is born. Voilà!
Log in using your favourite account and write your comments here