Test Planning - Test Strategy
Posted On 17 January, 2008 at 12:54 PM by Rajeev PrabhakaranActual writing of a strategy involves aspects, which define other issues between the Testing organization and the client. Testers must basically understand some of the issues that are discussed in the strategy document, which are outlined below
1. End-to-End: The test path uses the entire flow provided in the application for completion of a specified task. Within this process various test conditions and values are covered and results analyzed. There maybe a possibility of reporting several defects relating to the segments while covering the test path. The advantage of using this approach is to minimize combination and permutation of conditions/values and ensure coverage and integration.
2. Automation Strategy: Automation of testing process is done to reduce the effort during regression testing. In some cases automating the entire testing process may not possible due to technical and time constraints.
3. Performance Strategy: The client specifies the standards for the performance testing. It generally contains
• Response time
• Number of Virtual Users Using the above information, a Usage Pattern of the application is derived and documented in the strategy.
4. Risk Analysis: Risk's associated with projects are analyzed and mitigation's are documented in this document,
Schedule Risk: Factors that may affect the schedule of testing are discussed.
Technology Risk: Risks on the hardware and software of the application are discussed here
Resource Risk: Test team availability on slippage of the project schedule is discussed.
Support Risk: Clarifications required on the specification and availability of personnel for the same is discussed.
5. Effort Estimation: The function points in the Functional Specifications will be used as the basis for the purpose of estimating the effort needed for the project. The average of the different estimates from the Peers in the test team will be taken as the basis for calculation of the effort required.
6. Infrastructure: Hardware and software requirements for the testing the application are documented. Apart from this, any other requirement should also be documented. Infrastructure that has to be provided by the client is also specified.
1. End-to-End: The test path uses the entire flow provided in the application for completion of a specified task. Within this process various test conditions and values are covered and results analyzed. There maybe a possibility of reporting several defects relating to the segments while covering the test path. The advantage of using this approach is to minimize combination and permutation of conditions/values and ensure coverage and integration.
2. Automation Strategy: Automation of testing process is done to reduce the effort during regression testing. In some cases automating the entire testing process may not possible due to technical and time constraints.
3. Performance Strategy: The client specifies the standards for the performance testing. It generally contains
• Response time
• Number of Virtual Users Using the above information, a Usage Pattern of the application is derived and documented in the strategy.
4. Risk Analysis: Risk's associated with projects are analyzed and mitigation's are documented in this document,
Schedule Risk: Factors that may affect the schedule of testing are discussed.
Technology Risk: Risks on the hardware and software of the application are discussed here
Resource Risk: Test team availability on slippage of the project schedule is discussed.
Support Risk: Clarifications required on the specification and availability of personnel for the same is discussed.
5. Effort Estimation: The function points in the Functional Specifications will be used as the basis for the purpose of estimating the effort needed for the project. The average of the different estimates from the Peers in the test team will be taken as the basis for calculation of the effort required.
6. Infrastructure: Hardware and software requirements for the testing the application are documented. Apart from this, any other requirement should also be documented. Infrastructure that has to be provided by the client is also specified.
