Hey guys
What is test Strategy? And what is different between test Strategy and test plan?
Thanks
Hey guys
What is test Strategy? And what is different between test Strategy and test plan?
Thanks
Re: Different between test Strategy and test plan?
Hi newhere, a test plan encompasses a test strategy often. Test plan would cover the entire planning associated with testing life cyle. It would cover stuff like -
1) application description
2) test strategy
3) execution schedule
4) entry and exit criterias
5) testing environment
6) resource allocation
7) roles and responsibilities
8) assumptions
9) risks
10) communication and reporting.
Test strategy would cover the actual approach being used for testing as well as scope of testing. What are the functionalities that need to be covered as part of this testing plan as well what would be out of scope is also listed.
When i say approach to testing, it pertains as to what are the methodologies of testing we plan to implement. We could start with module level testing - have some signoff criteria based on which we proceed ahead to intergration testing and then move on to system testing. we could also list out the Testing tools that would be used as part of testing.
Most companies integrate test strategy as part of test plan and hence we wont find 2 seperate documents.
Cheers....
Last edited by bizzzzzare; 11-28-2007 at 02:48 PM. Reason: Better Readability
What is difference b/w testing strategy and testing approach?
Regards,
Brijesh Jain
---------------------------------------------------------
Connect with me on Skype: jainbrijesh
Google Plus : jainbrijeshji
Test plan and the test strategy are the documents that will be prepared ahead of the test execution of a project or a build.
Mostly, test plan will be prepared before the testing activity starts on a project and have the contents such as what are the builds that are going to be deployed and when it is scheduled. For example, changes or updates will be done for the application in a schedule manner where the iterative method is followed as sdlc. For each and every change scheduled in a build will be tested after its deployment.
Test plan is a road map document for the entire testing activity, whereas, the test strategy document will deals with the strategic approach that will be followed for handling each and every build or version.
Mostly, both the document will have the same contents with slight changes or modificaitons.
Test plan document will cover the following topics,
application description
objective
test strategy
schedule
environment
resource allocation
roles and responsibilities
levels of testing
assumptions
risks and the mitigation
risk contingency plans
In the test strategy document it will have the contents mentioned above along with
current situation of the system
system after the changes done
types of testing
new technical or business requirements added
system changes
entry and exit criterias
roles and responsibilities
rag factor
coverage criteria
I think it also depends for which company/shop you work. In my last project, Test Strategy and Test Plan were used interchangeably.
Test Plan is a parent document which includes whats the scope, objective, assumption, Project/Product details, resources, roles-responsibilities & configurations for testing
Test Strategy is Child Document which covers, what are the different types of Testing will be done, When these different testing started in testing, what is the entry/exit criteria, Tools, methods, which module first & which is to tested next.
Posting Permissions
Reply With Quote