A complete test plan has the same sorts of information as any other good plan. It defines what will be done and what will not. It also estimates resources that will be required, as well as a schedule of activities. It establishes a basis for managing the testing activities, reporting status and mitigating testing risks.
This software testing training course will teach you how to do a complete job of planning your test activities. It will walk you through the test planning process, identify all of the inputs you will need and the things you should produce. It will give you guidance on how to plan for test case creation, defect tracking, status monitoring and progress reporting. This course will equip you with all the tools you need to create a test plan that will serve all your needs.
Who Should Attend
I. The Test Planning Process
Test planning cannot be done in a vacuum. The test plan must integrate smoothly with all the other project plans and consider many variables, both within the testing group and throughout the rest of the organization.
II. Test Plan: Scope and Lifecycle
What is and is not included in the testing activities can be the subject of many disagreements; therefore, the test plan must be explicit about the scope of the testing activities and the testing lifecycle.
III. Test Plan:Traceability Matrix
The only way to assure that the test plan covers all of the requirements and goals without unnecessary tests is to have a systematic way to map tests and test cases to those requirements and objectives. Including a traceability matrix with the test plan is the easiest way to satisfy this need.
IV. Test Plan: Required Tests
Before test cases can be identified, the system requirements and testing objectives must be used to compile a list of tests that will be required. This list of tests is the heart of the test plan.
V. Test Plan:Test Cases
Actually writing test cases and preparing the related data consumes a significant amount of time. Therefore it is important to estimate and plan for these activities.
VI. Test Plan:Test Case Size Estimates
In order to provide a basis for planning the effort, costs and other resources needed for testing, we must estimate the size of each test case and document this in the test plan.
VII. Test Plan: Resources
Resources to support testing go far beyond just the people who will do the testing. The test plan must account for all required resources.
VIII. Test Plan: Effort, Cost, Budget & Schedule
Effort, cost, budget and schedule are usually the items we are asked to provide. But until all of the items in sections II through VII have been identified and estimated, we do not have the information we need to provide these things. These critical parts of the test plan can now be completed.
IX. Test Plan: Risks
Testing activities have their own unique risks that may not be visible or pertinent to other stakeholders in the project. The testing group should engage in risk management to assure that those items are handled appropriately and included in the test plan.
X. Test Plan: Management,Tracking & Reporting
The test plan must identify how the testing group will maintain control over the testing activities and assure that they are progressing as planned. It must also define how they will report status to other project stakeholders and take corrective actions when necessary.
A practical exposure to software testing.