Assignment 3
CpSc 873
Test Plans
The tests conducted during a project can cost anywhere from 50% to 200% of the cost of actually developing the application software. Therefore it is necessary that this activity (just like the development process) be carefully planned. The first activity is to plan the test process. This plan provides the context within which the testing activities of the project are conducted. Below is the outline of the documentation for the test process as specified in the IEEE 829 standard.
1.0 Introduction
2.0 Test Items
3.0 Tested Features
4.0 Features Not Tested (per cycle)
5.0 Testing Strategy and Approach
5.1 Syntax
5.2 Description of Functionality
5.3 Arguments for tests
5.4 Expected Output
5.5 Specific Exclusions
5.6 Dependencies
5.7 Test Case Success/Failure Criteria
6.0 Pass/Fail Criteria for the Complete Test Cycle
7.0 Entrance Criteria/Exit Criteria
8.0 Test Suspension Criteria and Resumption Requirements
9.0 Test Deliverables/Status Communications Vehicles
10.0 Testing Tasks
11.0 Hardware and Software Requirements
12.0 Problem Determination and Correction Responsibilities
13.0 Staffing and Training Needs/Assignments
14.0 Test Schedules
15.0 Risks and Contingencies
Read the material located at
http://members.tripod.com/~bazman/frame.html. It provides a set of three documents that should be created. Two of these require information that you can not yet provide. The system test plan, however, should be doable.The assignment is to develop the first iteration of a test plan for the development of the Brickles application. The plan will be updated as the project progresses. The information and scenarios developed for the previous assignment can be used as the basis for test cases
Due: February 8, 1999 prior to 6 pm. Use Word format. Use the handin command in the following form:
/usr/local/bin/handin.873.1