Page 185 -

the “Features to be Tested” section of the test plan. This section should contain the com-
plete Name field of each test case and base state. Typically, the test cases and base states
appear in the test case document in the same order that they appear in the test plan.
The test case document should have an outline that follows the software requirements
specification: it should contain one section for each use case and requirement, and in that
section, there should be a set of test cases that fully test that requirement. This makes the
test cases much easier to inspect, because a reviewer can look at a single section and judge
whether the test cases in that section fully exercise the requirement that they are sup-
posed to be testing.

Once the test cases are complete, they should be inspected by the engineering team (see
Chapter 5). The test plan and test cases should be collaborative documents; if the team does
not give input into them, then it is likely that the software will fail to implement certain
behavior that the users expect. This inspection will generally have a narrower audience than
the test plan because the document is much longer and more technical. Minimally, it should
be reviewed by another software tester, the requirements engineer who built the require-
ments that are being tested, and the programmer who implemented them.
Inspection Checklist

The following checklist items apply to the test plan.
Completeness
Does the document meet all established templates and standards?
Is the document complete?
Are there any requirements that are not tested?
Are there any features that are planned for testing but should be excluded?
Feasibility
Can the testing as planned be accomplished within the known cost and schedule con-
straints?

Can every test described in the test plan be reasonably conducted?
Environment

Is the description of the environment complete?
Is the test plan traceable to any nonfunctional requirements that define the operating
environment?
Performance
Does the test plan account for the expected load for concurrent users, large databases,
or other performance requirements?
Can the performance tests be traced back to requirements in the specification?

Acceptance Criteria
Do the acceptance criteria match the standards of the organization?

SOFTWARE TESTING 177