Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Items that are intended to stay in as part of your document are in bold; explanatory comments are in italic text. Plain text is used where you might insert wording about your project.
This document is an annotated outline for a Software Test Plan, adapted from the IEEE Standard for Software Test Documentation (Std 829-1998). Tailor as appropriate. Where you decide to omit a section, you might keep the header, but insert a comment saying why you omit the element.
Agency Name
Project Name
Software Quality Assurance Plan
Version: (n)
Date: (mm/dd/yyyy)
1. Revision History
Revision # Revision Date Description of Change Author
2. Distribution
Recipient Name Recipient Organization Distribution Method
TABLE OF CONTENTS
1. INTRODUCTION ....................................................................................................................................................1
2. TEST ITEMS ...........................................................................................................................................................3 3. FEATURES TO BE TESTED ...............................................................................................................................4 4. FEATURES NOT TO BE TESTED ......................................................................................................................4 5. APPROACH ............................................................................................................................................................4 6. PASS / FAIL CRITERIA ........................................................................................................................................6 7. TESTING PROCESS .............................................................................................................................................7 8. ENVIRONMENTAL REQUIREMENTS ...............................................................................................................8 9. CHANGE MANAGEMENT PROCEDURES .......................................................................................................9 10. PLAN APPROVALS ..........................................................................................................................................10
10/16/2012
9:38:40 PM
1. INTRODUCTION
(NOTE 1: THE SOFTWARE TEST PLAN GUIDELINES WERE DERIVED AND DEVELOPED FROM IEEE STANDARD FOR SOFTWARE TEST DOCUMENTATION (829-1998)). (Note 2: The ordering of Software Test Plan (STP) elements is not meant to imply that the sections or subsections must be developed or presented in that order. The order of presentation is intended for ease of use, not as a guide to preparing the various elements of the Software Test Plan. If some or all of the content of a section is in another document, then a reference to that material may be listed in place of the corresponding content.) The Introduction section of the Software Test Plan (STP) provides an overview of the project and the product test strategy, a list of testing deliverables, the plan for development and evolution of the STP, reference material, and agency definitions and acronyms used in the STP. The Software Test Plan (STP) is designed to prescribe the scope, approach, resources, and schedule of all testing activities. The plan must identify the items to be tested, the features to be tested, the types of testing to be performed, the personnel responsible for testing, the resources and schedule required to complete testing, and the risks associated with the plan.
1.1 Objectives
(Describe, at a high level, the scope, approach, resources, and schedule of the testing activities. Provide a concise summary of the test plan objectives, the products to be delivered, major work activities, major work products, major milestones, required resources, and master high-level schedules, budget, and effort requirements.)
Purpose for this level of test, Items to be tested, Features to be tested, Features not to be tested, Management and technical approach, Pass / Fail criteria, Individual roles and responsibilities, Milestones, Schedules, and Risk assumptions and constraints.
1.3 Scope
(Specify the plans for producing both scheduled and unscheduled updates to the Software Test Plan (change management). Methods for distribution of updates shall be specified along with version control and configuration management requirements must be defined.) Testing will be performed at several points in the life cycle as the product is constructed. Testing is a very 'dependent' activity. As a result, test planning is a continuing activity performed throughout the system development life cycle. Test plans must be developed for each level of product testing.
interpret the Software Test Plan. Reference may be made to the Glossary of Terms on the IRMC web page.)
2. TEST ITEMS
(Specify the test items included in the plan. Supply references to the following item documentation: Requirements specification, Design specification, Users guide, Operations guide, Installation guide, Features (availability, response time), Defect removal procedures, and Verification and validation plans.)
10/16/2012
9:38:40 PM
3. FEATURES TO BE TESTED
(Identify all software features and combinations of software features to be tested. Identify the test design specifications associated with each feature and each combination of features.)
5. APPROACH
1. THE VARIOUS TESTING THAT WILL be performed are as follows: Regression testing Unit testing System testing Component testing Integration testing Interface testing Security testing Performance testing 2. The testing will be performed on the most risky and important part of the software initially and then will move ahead to the less risky parts. 3. There is a must have, should have, could have approach to the priority of new functionality and so the test approach should take this into account? 4. Rapid-test techniques such as exploratory testing to get an early assessment of the stability of the software will be used. 5. Regression tests will be carried out manually. 6. The time for the regression testing should be inside the time frame.
10/16/2012
9:38:40 PM
10/16/2012
9:38:40 PM
7. TESTING PROCESS
Identification of the methods and criteria used in performing test activities are mentioned here. In this part definition of the specific methods and procedures for each type of test is done and also definition of the detailed criteria for evaluating test results are mentioned.
7.3 Responsibilities
This issue includes who is responsible for all areas of the plan. They are as follows: 1. Setting risks: This will be done together by the project manager and designing team with the help of the customer. 2. Selecting features to be tested and not tested: This will be performed by the system design team with the help of the testing teams 3. Setting overall strategy for this level of plan.: This will be performed by the project manager with the design team. 4. Ensuring all required elements are in place for testing: This is performed by the coding team 5. Who provides the required training : This is decided by the human resource head 6. Who makes the critical go/no go decisions for items not covered in the test plans : This is done by the project manager.
7.4 Resources
(Identify the resources allocated for the performance of testing tasks. Identify the organizational elements or individuals responsible for performing testing activities. Assign specific responsibilities. Specify resources by category. If automated tools are to be used in testing, specify the source of the tools,
10/16/2012 9:38:40 PM
7.5 Schedule
Time has been allocated within the project plan for the following testing activities. The specific dates and times for each activity are defined in the project plan time line. The persons required for each process are detailed in the project time line and plan as well. Coordination of the personnel required for each task, test team, development team, management and customer will be handled by the project manager in conjunction with the development and test team leaders. A. Review of Requirements document by test team personnel (with other team members) and initial creation of Inventory classes, sub-classes and objectives. B. Development of Master test plan by test manager and test with time allocated for at least two reviews of the plan. C. Review of the System design document by test team personnel. This will provide the team with a clearer understanding of the application structure and will further define the Inventory classes, sub-classes and objectives. D. Development of System/Integration and Acceptance test plans by test manager and other essential personnel with time allocated for at least two reviews of the plans. E. Review of the Detail design document(s) by test team personnel as required. This will provide the team with a clearer understanding of the individual program structure and will further define the Inventory classes, sub-classes and objectives. F. Unit test time within the development process. G. Time allocated for both System/Integration and Acceptance test processes.
8. ENVIRONMENTAL REQUIREMENTS
Both the necessary and desired properties of the test environment including the physical characteristics, communications, mode of usage, and testing supplies are the environmental requirements. Also the levels of security required to perform test activities.
8.1 Hardware
The different hardware needed are : 1. Any Windows operating system
8.2 Software
(Identify the software requirements needed to complete testing activities.)
8.3 Tools
The different tools used are:
Description: PeopleSoft offers customizable packages for business use, including accounting, materials management, distribution, manufacturing, and human resources. Rational has taken much of SQA Suite and integrated it with PeopleSoft packages, including some new customized features 2. Name: Visual Test Description: Test cases and suites described as program (in special TestBasic language) rather than scripts. Develop test programs, manage suites of tests. May write tests by hand or Scenario Recorder can record session and make into a test (capture & playback). Tests created by the Scenario Recorder can be edited. Can write failure tests to catch exceptions. System testing only, not unit testing.
Testing Levels The testing for the Reassigned Sales project will consist of Unit, System/Integration (combined) and Acceptance test levels. It is hoped that there will be at least one full time independent test person for system/integration testing. However, with the budget constraints and time line established; most testing will be done by the test manager with the development teams participation. UNIT Testing will be done by the developer and will be approved by the development team leader. Proof of unit testing (test case list, sample output, data printouts, defect information) must be provided by the programmer to the team leader before unit testing will be accepted and passed on to the test person. All unit test information will also be provided to the test person. SYSTEM/INTEGRATION Testing will be performed by the test manager and development team leader with assistance from the individual developers as required. No specific test tools are available for this project. Programs will enter into System/Integration test after all critical defects have been corrected. A program may have up to two Major defects as long as they do not impede testing of the program (I.E. there is a work around for the error). ACCEPTANCE Testing will be performed by the actual end users with the assistance of the test manager and development team leader. The acceptance test will be done in parallel with the existing manual ZIP/FAX process for a period of one month after completion of the System/Integration test process. Programs will enter into Acceptance test after all critical and major defects have been corrected. A program may have one major defect as long as it does not impede testing of the program (I.E. there is a work around for the error). Prior to final completion of acceptance testing all open critical and major defects MUST be corrected and verified by the Customer test representative. A limited number of distributors will participate in the initial acceptance test process. Once acceptance test is complete, distributors will be added as their ability to generate the required EDI data is verified and checked against their FAX/ZIP data. As such, some distributors will be in actual production and some in parallel testing at the same time. This will require careful coordination
8.4 Publications
The different IEEE documents can be used for reference during testing
3. Late delivery of the software, hardware or tools. 4. Delays in training on the application and/or tools. 5. Changes to the original requirements or designs. The solutions for all these risks are as follows: 1. Requirements definition will be complete by January 1, 19XX, and, if the requirements change after that date, the following actions will be taken. 2. The test schedule and development schedule will move out an appropriate number of days. This rarely occurs, as most projects tend to have fixed delivery dates. 3. The number of test performed will be reduced. 4. The number of acceptable defects will be increased. 5. These two items could lower the overall quality of the delivered product. 6. Resources will be added to the test team. 7. The test team will work overtime. 8. The scope of the plan may be changed. 9. There may be some optimization of resources. This should be avoided, if possible,
10/16/2012
9:38:40 PM
10