Test Suite Construction
From dis-Emi-A
Once a module or feature has been isolated and selected for testing it is time to actually design the tests for that item. The collection of tests associated with a given feature, or module, is known as a Test Suite. This is fairly common term, though in some contexts has a slightly differing meaning.
Contents |
Outline
The following is the general outline to createing a test suite for a particular feature.
Identify Features
Review the entire user story in which each feature resides in order to clearly understand how the feature is intended to work and whatever features may be testable at the same time.
Record what the setup procedure is required in order to test.
Chart Flow
The primary flow of a requirement is based on the transitions from one state to another. These may be from screens of the application, or internal processing modes. In this step we are interested in producing the most basic form of this flowchart.
Refer to Test Flowchart for complete instructions.
Identify Inputs
Identify and classify the inputs at all steps.
Refer to Input classification.
Setup Cause-Effect Graph
Assemble the list of all to-be-tested inputs from the input list and enter them on the cause-effect graph. Construct the first few three levels of the Equivalence Classes for each of these inputs.
At this time only enter inputs which you know will be tested, and only expand the classes are far as you are certain will be tested. The cause-effect graph can be extended later as need and time require/allow.
Identify Outputs / Effects
In addition to the inputs, all outputs and effects should be accounted for. These may exist on the flowchart and/or the cause-effect graph, depending on which is more appropriate.
Determine Influential Features
Refer to (and update) the Input Map to determine influential features based on the identified inputs. Additional classes of interest should be added to the equivalence classes of the relevant input.
Prioritize And Test
All flowchart paths should be tested, but the inputs are subject to prioritization. Refer to Test Suite Prioritization for prioritization of the remainder.
