Test Plan

Class Name Class Code Group Teacher Project Manager Assign Date Complete Date Author Version Approved By Approved Date

Table of Content 1. Introduction 1.1 Purpose 1.2 Scope 1.3 Intended Audience 1.4 Supporting Materials 1.5 References 2. Test Strategy 2.1.1 <Feature> Description 2.1.2 Testing Strategy 3. Test Plan 3.1 Requirements for Test 3.2 Type of Test 3.2.1 Unit Testing 3.2.1.1 3.2.1.2 3.2.1.3 3.2.2 Integration Testing 3.2.2.1 3.2.2.2 3.2.2.3 3.2.3 System Testing 3.2.3.1 3.2.3.2 3.2.3.3 3.3 Environment Needs 3.3.1 Hardware requirements 3.3.2 Software requirements 3.3.3 Other test tool requirements 4. Schedule

3 3 3 3 3 3 3 3 3 4 4 4 4 Requirements to be Tested Expected Result Test Criteria 4 Requirements to be tested Expected Result Test Criteria 5 Requirements to be Tested Expected Result Test Criteria 5 5 5 5 5

4 4 4 4 5 5 5 5 5

Introduction
Purpose Scope 1.1.1 Data Enty The uploading system allow user to upload book and enter books information from browser.The system will be form driven and will provide error messages to help direct user through various options. 1.1.2 Report 1.1.3 File Tranfer One Book is entered into a DataBase 1.1.4 Security Each user need a userid and password to login to system Intended Audience Supporting Materials

The following references are cited in this document: [SDS] Please refer to the latest approved version of the document <Put SDS title here>. [DDS] Please refer to the latest approved version of the document <Put DDS title here>. (Optional) Note any references or related materials here. (Some other technical documents like: IETF, RFC that you mentioned above.) This section should be organized in a table.
References y System Design Specification, revision x.x y Detailed Design Specification, revision x.x y Remove this section because we already have 1.4 2. Test Strategy <Feature> Description Testing Strategy 2.1.1.1 Unit Test 2.1.1.2 System Test

2.1.1.3 Perform Test

Test Plan Requirements for Test

[The information below identifies those items (use cases, functional requirements, non-functional requirements) that have been identified as targets for testing. From a high level this represents what will be tested For example: 2.1.1 Use Cases # Use case # Name

2.1.2 Use Diagram Insert the use case diagram here. 2.1.3 Functional Requirements List out the functional requirements that need for testing 2.4 Non-functional Requirements List out the non-functional requirements that need for testing
Type of Test Unit Testing Requirements to be Tested

[Describe the system and program requirements that will be tested with unit test]
Expected Result

[Describe the expected results of the testing performed.] Test Criteria [Describe the criteria to perform, suspend, and exit the unit test.] Integration Testing Specify requirements and criteria to ensure all features a re integrated successfully. We mainly focus on interface test cases and fictional test cases to make sure all feature requirements are covered.
Requirements to be tested

[Describe the system and program requirements that will be tested with integration test]

Expected Result

[Describe the expected results of the testing performed.]

 Hardware/software is not available at the times indicated in the project schedule.  Source code contains one or more critical defects, which seriously prevents or limits testing progress.  Assigned test resources are not available when needed by the test tea m. System Testing Specify requirements and criteria to ensure all key functions are work correctly. Test cases are selected from System Testing test case only. Refer to section for details
Requirements to be Tested

[Describe the system and program requirements that will be tested with iteration test]
Expected Result

[Describe the expected results of the testing performed.]

[Describe the criteria to perform, suspend, and exit the System test.]
Environment Needs Hardware requirements - 20 PC - 4G Ram - 160 G HDD - Internet - 100 user id and password Software requirements - Windows xp (user supply) - Browser - Database managerment system Other test tool requirements Schedule

Unit test:01/9/2011-02/9/2011 System Test:4/9/2011-5/9/2011

Acception Test:6/9/2011-7/9/2011 ---------- End of Document ----------