Definition of test items

Define the test items you intend to test within the scope of this test plan. 

Essentially, something you will test is a list of what is to be tested. This can be 

developed from the software application inventories as well as other sources of 

documentation and information.

This section is a technical description of the software, and can be oriented to the 

level of the test plan. For higher levels, it may be by application or functional area, 

for lower levels it may be by program, unit, module, or build.

Features to be tested

This is a listing of what is to be tested from the user's viewpoint of what the 

system does. This is not a technical description of the software, but a user's view 

of the functions. Users do not understand technical software terminology. They 

understand functions and processes as they relate to their jobs.

Set the level of risk for each feature. Use a simple rating scale such as high, 

medium, and low (H, M, L). These types of levels are understandable to a user. 

You should be prepared to discuss why a particular level was chosen.

Features not to be tested

This is a listing of what is 

not

to be tested from both the user's viewpoint of what 

the system does, and a configuration management view. This is not a technical 

description of the software, but a user's view of the functions.

Identify 

why

the feature is not to be tested; there can be any number of reasons.

Test strategy

This is your overall test strategy for this test plan. It should be appropriate to the 

plan and should be in agreement with plans affecting application and database 

parts. Overall rules and processes should be identified:

Are any special tools to be used and what are they?

Will the tool require special training?

What metrics will be collected?

Which level is each metric to be collected at?

How is configuration management to be handled?

How many different configurations will be tested?

Which combinations of hardware, software, and other vendor packages are 

used?

 Chapter 9. Testing and tuning 

265