This is a summary of the ANSI/IEEE Standard 829-1983. It describes a test plan as:
"A document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning."
This standard specifies the following test plan outline:
Test Plan Identifier:
1. A unique identifier
Introduction
1. Summary of the items and features to be tested
2. Need for and history of each item (optional)
3. References to related documents such as project authorization, project plan, QA plan, configuration management plan, relevant policies, relevant standards
4. References to lower level test plans
Test Items
1. Test items and their version
2. Characteristics of their transmittal media
3. References to related documents such as requirements specification, design specification, users guide, operations guide, installation guide
4. References to bug reports related to test items
5. Items which are specifically not going to be tested (optional)
Features to be Tested
1. All software features and combinations of features to be tested
2. References to test-design specifications associated with each feature and combination of features
Features Not to Be Tested
1. All features and significant combinations of features which will not be tested
2. The reasons these features won't be tested
Approach
1. Overall approach to testing
2. For each major group of features of combinations of features, specify the approach
3. Specify major activities, techniques, and tools which are to be used to test the groups
4. Specify a minimum degree of comprehensiveness required
5. Identify which techniques will be used to judge comprehensiveness
6. Specify any additional completion criteria
7. Specify techniques which are to be used to trace requirements
8. Identify significant constraints on testing, such as test-item availability, testing-resource availability, and deadline
Item Pass/Fail Criteria
1. Specify the criteria to be used to determine whether each test item has passed or failed testing
Suspension Criteria and Resumption Requirements
1. Specify criteria to be used to suspend the testing activity
2. Specify testing activities which must be redone when testing is resumed
Test Deliverables
1. Identify the deliverable documents: test plan, test design specifications, test case specifications, test procedure specifications, test item transmittal reports, test logs, test incident reports, test summary reports
2. Identify test input and output data
3. Identify test tools (optional)
Testing Tasks
1. Identify tasks necessary to prepare for and perform testing
2. Identify all task interdependencies
3. Identify any special skills required
Environmental Needs
1. Specify necessary and desired properties of the test environment: physical characteristics of the facilities including hardware, communications and system software, the mode of usage (i.e., stand-alone), and any other software or supplies needed
2. Specify the level of security required
3. Identify special test tools needed
4. Identify any other testing needs
5. Identify the source for all needs which are not currently available
Testing is performed using hardware with the following minimum system requirements:
1. 133 MHz Pentium
2. Microsoft Window, 98
3. 32 MB RAM
4. 10 MB available hard disk space
5. A display device capable of displaying 640x480 (VGA) or better resolution .
6. Internet connection via a modem or network.
Responsibilities
1. Identify groups responsible for managing, designing, preparing, executing, witnessing, checking and resolving
2. Identify groups responsible for providing the test items identified in the Test Items section
3. Identify groups responsible for providing the environmental needs identified in the Environmental Needs section
Staffing and Training Needs
1. Specify staffing needs by skill level
2. Identify training options for providing necessary skills
Schedule
1. Specify test milestones
2. Specify all item transmittal events
3. Estimate time required to do each testing task
4. Schedule all testing tasks and test milestones
5. For each testing resource, specify its periods of use
Testing scheduling and status reporting are performed by the Project Lead and project Administrator to monitor progress towards meeting product testing schedules and release date, as well as to identify any project scheduling risks. Each build will be tested before next subsequent build date. Software testing schedules will coincide with module development and release schedules
Risks and Contingencies
1. Identify the high-risk assumptions of the test plan
2. Specify contingency plans for each
Approvals
1. Specify the names and titles of all persons who must approve the plan
2. Provide space for signatures and dates
"A document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning."
This standard specifies the following test plan outline:
Test Plan Identifier:
1. A unique identifier
Introduction
1. Summary of the items and features to be tested
2. Need for and history of each item (optional)
3. References to related documents such as project authorization, project plan, QA plan, configuration management plan, relevant policies, relevant standards
4. References to lower level test plans
Test Items
1. Test items and their version
2. Characteristics of their transmittal media
3. References to related documents such as requirements specification, design specification, users guide, operations guide, installation guide
4. References to bug reports related to test items
5. Items which are specifically not going to be tested (optional)
Features to be Tested
1. All software features and combinations of features to be tested
2. References to test-design specifications associated with each feature and combination of features
Features Not to Be Tested
1. All features and significant combinations of features which will not be tested
2. The reasons these features won't be tested
Approach
1. Overall approach to testing
2. For each major group of features of combinations of features, specify the approach
3. Specify major activities, techniques, and tools which are to be used to test the groups
4. Specify a minimum degree of comprehensiveness required
5. Identify which techniques will be used to judge comprehensiveness
6. Specify any additional completion criteria
7. Specify techniques which are to be used to trace requirements
8. Identify significant constraints on testing, such as test-item availability, testing-resource availability, and deadline
Item Pass/Fail Criteria
1. Specify the criteria to be used to determine whether each test item has passed or failed testing
Suspension Criteria and Resumption Requirements
1. Specify criteria to be used to suspend the testing activity
2. Specify testing activities which must be redone when testing is resumed
Test Deliverables
1. Identify the deliverable documents: test plan, test design specifications, test case specifications, test procedure specifications, test item transmittal reports, test logs, test incident reports, test summary reports
2. Identify test input and output data
3. Identify test tools (optional)
Testing Tasks
1. Identify tasks necessary to prepare for and perform testing
2. Identify all task interdependencies
3. Identify any special skills required
Environmental Needs
1. Specify necessary and desired properties of the test environment: physical characteristics of the facilities including hardware, communications and system software, the mode of usage (i.e., stand-alone), and any other software or supplies needed
2. Specify the level of security required
3. Identify special test tools needed
4. Identify any other testing needs
5. Identify the source for all needs which are not currently available
Testing is performed using hardware with the following minimum system requirements:
1. 133 MHz Pentium
2. Microsoft Window, 98
3. 32 MB RAM
4. 10 MB available hard disk space
5. A display device capable of displaying 640x480 (VGA) or better resolution .
6. Internet connection via a modem or network.
Responsibilities
1. Identify groups responsible for managing, designing, preparing, executing, witnessing, checking and resolving
2. Identify groups responsible for providing the test items identified in the Test Items section
3. Identify groups responsible for providing the environmental needs identified in the Environmental Needs section
Staffing and Training Needs
1. Specify staffing needs by skill level
2. Identify training options for providing necessary skills
Schedule
1. Specify test milestones
2. Specify all item transmittal events
3. Estimate time required to do each testing task
4. Schedule all testing tasks and test milestones
5. For each testing resource, specify its periods of use
Testing scheduling and status reporting are performed by the Project Lead and project Administrator to monitor progress towards meeting product testing schedules and release date, as well as to identify any project scheduling risks. Each build will be tested before next subsequent build date. Software testing schedules will coincide with module development and release schedules
Risks and Contingencies
1. Identify the high-risk assumptions of the test plan
2. Specify contingency plans for each
Approvals
1. Specify the names and titles of all persons who must approve the plan
2. Provide space for signatures and dates
No comments:
Post a Comment