1.0 IDENTIFICATION
1.1
1.2
1.3
1.4
1.5
1.6
Test Procedure Number:
Test Requirement Identification (Reference):
Test Name:
Location:
Test Author:
Test Date:
TP-11
InterfaceView Unit Test
UMB CS UNIX Lab.
J. Hill
3/21/98
2.0 TEST DESCRIPTION
2.1 Purpose
The purpose of this test is to verify the detailed requirements of the
InterfaceView class at a unit level. Our intention is to accomplish the
verification by means of a “code walkthrough.” That is, we as a team
including the author will formally read through the code step-by-step. The
logic will be examined and supporting data structures/representations will be
evaluated for their ability to accomplish the unit responsibilities as defined by
the Classes, Responsibilities, Helpers (CRH) cards prepared and furnished as
part of the Engineering Requirements Specification (ERS).
2.2 Test Method
The method selected for this test is Inspection.
2.3 Constraints
None.
3.0 TEST PROCEDURE REQUIREMENTS
3.1
3.2
3.3
3.4
Test Duration:
Materials:
Test Order:
System Version
.75 hours
ERS, dated 12/16/97.
No predefined order required.
Version 1.0
4.0 TEST PROCEDURE
4.1 Test Steps
a.
b.
c.
d.
e.
Log on to the Computer Science (CS) UNIX network.
Select a valid computer, e.g., “eris”
Set the default directory to “slang.”
Print copies of the source code listings of the file InterfaceView.java.
Log off the computer.
f. As a group, read the source code step-by-step.
g. Check and see if the responsibilities defined by the InterfaceView CRH
are performed.
h. Check and see if the code logic is coherent and does not leave dead-ends
and or produce invalid outputs under a range of all valid inputs.
i. Fill out appropriate Test Data Sheet and any other documentation
resulting from inspection of this code.
4.2 Descriptions of Expected Results
No pre-determined results are predicted for a Inspection method test.
4.3 Test Data Sheet