测试计划TestPlanSample2.docVIP

Software Test Plan March 13, 2003 Submitted By: Valerie Stanton Hatsey Frezghi Todd Wilkinson Nick Monge Table of Contents 1 Introduction 3 1.1 Team Interaction 3 2 Test Objective 3 3 Process Overview 3 4 Testing Process 4 5 Testing Strategy 5 5.1 Unit Testing 7 5.1.1 White Box Testing 7 5.1.2 Black Box Testing 10 5.2 Integration Testing 12 5.2.1 Incremental Testing 12 5.3 System Testing 12 5.3.1 Function Validation Testing 12 5.3.2 Performance testing 13 6 Entry and Exit Criteria 13 6.1 Unit Testing 14 6.1.1 Black Box Phase 14 6.1.2 White Box Phase 15 6.2 Integration Test 16 6.2.1 Integration Test Entry Criteria 16 6.2.2 Integration Test Exit Criteria 16 6.3 System Test 17 6.3.1 System Test Entry Criteria 17 6.3.2 System Exit Criteria 17 6.4 Shipping or Live Release 18 6.4.1 Shipping/Live Release Entry Criteria 18 6.4.2 Shipping/Live Release exit Criteria 18 7 Bug Tracking/ Bug Process 18 7.1 Various Roles in Bug Resolution 19 7.2 Bug Report Form 20 8 Roles and Responsibilities 21 8.1 Development Team 21 8.2 Testing Team 21 9 Test Schedule 21 10 Deliverables 23 11 References 24 Introduction This document is a high-level overview defining our testing strategy for the Sorted Binary Tree application. Its objective is to communicate project-wide quality standards and procedures. It portrays a snapshot of the project as of the end of the planning phase. This document will address the different standards that will apply to the unit, integration and system testing of the specified application. We will utilize testing criteria under the white box, black box, and system-testing paradigm. This paradigm will include, but is not limited to, the testing criteria, methods, and test cases of the overall design. Throughout the testing process we will be applying the test documentation specifications described in the IEEE Standard 829-1983 for Software Test Documentation. Team Interaction The following describes the level of team i