Test Manual

<<Project Name>>

Team Members:

Nelson Montalvo, Yenni Kwek, Eric Farng, Vincent Mak

15-612 Distributed Systems

Spring 1998

Carnegie Mellon University

Pittsburgh, PA 15213

Table of Contents

<<Hyperlinks to the sections, and in particular the tests described in this document>>

Objectives
Document References
Test Summary
Testing Strategy

Test A
Test B
Test C
Test D

Testing Schedule

Testing Materials

<<Instructions for filling out the template

Each team needs to describe 4+-2 test cases. Each test case must contain or refer to the following components:

• Test Specification
• Test Description
• Test Analysis Report
• Testng Schedule
• Test Materials

This document template assumes the description of 4 tests "Test A, Test B, Test C and Test D.

>>

Objectives

<<Describe the purpose of this document. Forecast the testing strategy, the unit tests, integration test and system tests listed in this document.

Document References

<<This section references the major documents produced during project development. Explains the relationships among the requirements documents, design documents, implementation documents and the test procedures.>>

Test Summary

<<Describe the functions of the system tested in this document (Refer to Requirements Analysis Document and Problem Statement)>>

Testing Strategy

The Testing Strategy defines the subsystem or subsystems to be tested, the system integration strategy and how, where, when, and by whom the tests will be conducted. You may want to include drawings depicting relationships among the major classes of the subsystem or the subsystem decomposition, if you feel this is appropriate.

Test A

<<Introduction and overview for test A>>

Test Specification

<<The Test Specification lists the requirements whose satisfaction will be demonstrated by the test. It lists the methods tested, and describes the conditions of the test. An example of a Test Specification is shown in Table 1 (from Pfleeger, Software Engineering, page 370).

Test Description

<<The Test Description is used as a guide in performing the test. It lists the input data and input commands for each test, as well as expected out put and system messages. If you find that you are unable to describe expected output numerically, use a natural language description. A test description consists of

• Location of test (full path name to the location in the Master Directory)
• Means of Control: Describes how data are entered (manually or automatically with a test driver)
• Data
• Input Data
• Input Commands
• Output Data
• System Messages
• Procedures: The test procedure is often specificed in form of a test script. An example of a test script can be found in Pfleeger, page 374

A sample description of the test data for a sort routine is shown in Pfleeger, Software Engineering, page 372.

Test Analysis Report

<<The Test Analysis Report lists the functions and performance characteristics that were to be demonstrated, and describes the actual test results. The description of the results must include the following:

• Function
• Performance
• Data measures, including whether target requirements have been met

If an error or deficiency has been discovered, the report discusses its impact.>>

Test B

<<Introduction and overview for test B>>

Test Specification

<<The Test Specification lists the requirements whose satisfaction will be demonstrated by the test. It lists the methods tested, and describes the conditions of the test. An example of a Test Specification is shown in Table 1 (from Pfleeger, Software Engineering, page 370).

Test Description

<<The Test Description is used as a guide in performing the test. It lists the input data and input commands for each test, as well as expected out put and system messages. If you find that you are unable to describe expected output numerically, use a natural language description. A test description consists of

• Location of test (full path name to the location in the Master Directory)
• Means of Control: Describes how data are entered (manually or automatically with a test driver)
• Data
• Input Data
• Input Commands
• Output Data
• System Messages
• Procedures: The test procedure is often specificed in form of a test script. An example of a test script can be found in Pfleeger, page 374

A sample description of the test data for a sort routine is shown in Pfleeger, Software Engineering, page 372.

Test Analysis Report

<<The Test Analysis Report lists the functions and performance characteristics that were to be demonstrated, and describes the actual test results. The description of the results must include the following:

• Function
• Performance
• Data measures, including whether target requirements have been met

If an error or deficiency has been discovered, the report discusses its impact.>>

Test C

<<Introduction and overview for test C>>

Test Specification

<<The Test Specification lists the requirements whose satisfaction will be demonstrated by the test. It lists the methods tested, and describes the conditions of the test. An example of a Test Specification is shown in Table 1 (from Pfleeger, Software Engineering, page 370).

Test Description

<<The Test Description is used as a guide in performing the test. It lists the input data and input commands for each test, as well as expected out put and system messages. If you find that you are unable to describe expected output numerically, use a natural language description. A test description consists of

• Location of test (full path name to the location in the Master Directory)
• Means of Control: Describes how data are entered (manually or automatically with a test driver)
• Data
• Input Data
• Input Commands
• Output Data
• System Messages
• Procedures: The test procedure is often specificed in form of a test script. An example of a test script can be found in Pfleeger, page 374

A sample description of the test data for a sort routine is shown in Pfleeger, Software Engineering, page 372.

Test Analysis Report

<<The Test Analysis Report lists the functions and performance characteristics that were to be demonstrated, and describes the actual test results. The description of the results must include the following:

• Function
• Performance
• Data measures, including whether target requirements have been met

If an error or deficiency has been discovered, the report discusses its impact.>>

Test D

<<Introduction and overview for test D>>

Test Specification

<<The Test Specification lists the requirements whose satisfaction will be demonstrated by the test. It lists the methods tested, and describes the conditions of the test. An example of a Test Specification is shown in Table 1 (from Pfleeger, Software Engineering, page 370).

Test Description

<<The Test Description is used as a guide in performing the test. It lists the input data and input commands for each test, as well as expected out put and system messages. If you find that you are unable to describe expected output numerically, use a natural language description. A test description consists of

• Location of test (full path name to the location in the Master Directory)
• Means of Control: Describes how data are entered (manually or automatically with a test driver)
• Data
• Input Data
• Input Commands
• Output Data
• System Messages
• Procedures: The test procedure is often specified in form of a test script. An example of a test script can be found in Pfleeger, page 374

A sample description of the test data for a sort routine is shown in Pfleeger, Software Engineering, page 372.

Test Analysis Report

<<The Test Analysis Report lists the functions and performance characteristics that were to be demonstrated, and describes the actual test results. The description of the results must include the following:

• Function
• Performance
• Data measures, including whether target requirements have been met

If an error or deficiency has been discovered, the report discusses its impact.>>

Test Materials

<<Describes materials required for executing the tests described in this document.>>