Sadasdasd

IEEE Test Plan Outline
Foundation Course in Software Testing

TEST PLAN OUTLINE (IEEE 829 FORMAT)
1) 2) 3) 4) 5) 6) 7) 8) 9) 10) 11) 12) 13) 14) 15) 16) 17) 18) 19) Test Plan Identifier References Introduction Test Items Software Risk Issues Features to be Tested Features not to be Tested Approach Item Pass/Fail Criteria Suspension Criteria and Resumption Requirements Test DeliverablesRemaining Test Tasks Environmental Needs Staffing and Training Needs Responsibilities Schedule Planning Risks and Contingencies Approvals Glossary

Prepared by Systeme Evolutif Limited

Page 1

IEEE Test Plan Outline
Foundation Course in Software Testing

IEEE TEST PLAN TEMPLATE
1 TEST PLAN IDENTIFIER
Some type of unique company generated number to identify this test plan, its level and thelevel of software that it is related to. Preferably the test plan level will be the same as the related software level. The number may also identify whether the test plan is a Master plan, a Level plan, an integration plan or whichever plan level it represents. This is to assist in coordinating software and testware versions within configuration management. Keep in mind that test plans are likeother software documentation, they are dynamic in nature and must be kept up to date. Therefore, they will have revision numbers. You may want to include author and contact information including the revision history information as part of either the identifier section of as part of the introduction.

2

REFERENCES
List all documents that support this test plan. Refer to the actualversion/release number of the document as stored in the configuration management system. Do not duplicate the text from other documents as this will reduce the viability of this document and increase the maintenance effort. Documents that can be referenced include: § § § § § § § Project Plan Requirements specifications High Level design document Detail design document Development and Test process standardsMethodology guidelines and examples Corporate standards and guidelines

3

INTRODUCTION
State the purpose of the Plan, possibly identifying the level of the plan (master etc.). This is essentially the executive summary part of the plan. You may want to include any references to other plans, documents or items that contain information relevant to this project/process. If preferable, you cancreate a references section to contain all reference documents. Identify the Scope of the plan in relation to the Software Project plan that it relates to. Other items may include, resource and budget constraints, scope of the testing effort, how testing relates to other evaluation activities (Analysis & Reviews), and possible the process to be used for change control and communication and coordinationof key activities. As this is the “Executive Summary” keep information brief and to the point.

4

TEST ITEMS (FUNCTIONS)
These are things you intend to test within the scope of this test plan. Essentially, something you will test, a list of what is to be tested. This can be developed from the software application inventories as well as other sources of documentation and information.Prepared by Systeme Evolutif Limited

Page 2

IEEE Test Plan Outline
Foundation Course in Software Testing

This can be controlled and defined by your local Configuration Management (CM) process if you have one. This information includes version numbers, configuration requirements where needed, (especially if multiple versions of the product are supported). It may also include key deliveryschedule issues for critical elements. Remember, what you are testing is what you intend to deliver to the Client. This section can be oriented to the level of the test plan. For higher levels it may be by application or functional area, for lower levels it may be by program, unit, module or build.

5

SOFTWARE RISK ISSUES
Identify what software is to be tested and what the critical areas are,...