Test Strategy Plan
PLease can anyone send me there test strategy , YOu can remove the company name if you want to...I need to write a test strategy but i have no idea.....i need an example to work on...
Re: Test Strategy Plan
This is your overall test strategy for this test plan; it should be appropriate to the level of
the plan (master, acceptance, etc.) and should be in agreement with all higher and lower
levels of plans. Overall rules and processes should be identified.
· Are any special tools to be used and what are they?
· Will the tool require special training?
· What metrics will be collected?
· Which level is each metric to be collected at?
· How is Configuration Management to be handled?
· How many different configurations will be tested
· Combinations of HW, SW and other vendor packages
· What are the regression test rules? How much will be done and how much at each test
· Will regression testing be based on severity of defects detected?
· How will elements in the requirements and design that do not make sense or are
untestable be processed?
· If this is a master test plan the overall project testing approach and coverage
requirements must also be identified.
· Specify if there are special requirements for the testing.
· Only the full component will be tested.
· A specified segment of grouping of features/components must be tested together.
· Other information that may be useful in setting the approach are:
· MTBF, Mean Time Between Failures - if this is a valid measurement for the test
involved and if the data is available.
· SRE, Software Reliability Engineering - if this methodology is in use and if the
information is available.
· How will meetings and other organizational processes be handled.
· Are there any significant constraints to testing.
· Resource availability
· Are there any recommended testing techniques that should be used, if so why?
Item Pass/Fail Criteria
What are the Completion criteria for this plan? This is a critical aspect of any test plan
and should be appropriate to the level of the plan. The goal is to identify whether or not a test
item has passed the test process.
· At the Unit test level this could be items such as:
· All test cases completed.
· A specified percentage of cases completed with a percentage containing some
number of minor defects.
· Code coverage tool indicates all code covered.
· At the Master test plan level this could be items such as:
· All lower level plans completed.
· A specified number of plans completed without errors and a percentage with
· This could be an individual test case level criterion or a unit level plan or it can be
general functional requirements for higher level plans.
· What is the number and severity of defects located?
· Is it possible to compare this to the total number of defects? This may be impossible,
as some defects are never detected.
· A defect is something that may cause a failure, and may be acceptable to leave in the
· A failure is the result of a defect as seen by the User, the system crashes, etc.
Hope this helps.