Test Analysis

Rather than consider test analysis and design together as described in the Foundation
Level syllabus, the advanced syllabi consider them as separate activities, albeit
recognizing that they can be implemented as parallel, integrated, or iterative activities
to facilitate the production of test design work products.

Test analysis is the activity that defines “what” is to be tested in the form of test
conditions. Test conditions can be identified by analysis of the test basis, test
objectives, and product risks. They can be viewed as the detailed measures and targets
for success (e.g., as part of the exit criteria) and should be traceable back to the test
basis and defined strategic objectives, including test objectives and other project or
stakeholder criteria for success. Test conditions should also be traceable forward to
test designs and other test work products as those work products are created.
Test analysis for a given level of testing can be performed as soon as the basis for
testing is established for that level. Formal test techniques and other general analytical
techniques (e.g., analytical risk-based strategies and analytical requirements-based
strategies) can be used to identify test conditions. Test conditions may or may not
specify values or variables depending on the level of testing, the information available
at the time of carrying out the analysis and the chosen level of detail (i.e., the degree of
granularity of documentation).

There are a number of factors to consider when deciding on the level of detail at which
to specify test conditions, including:
- Level of testing
- Level of detail and quality of the test basis
- System/software complexity
- Project and product risk
- The relationship between the test basis, what is to be tested and how it is to be
tested
- Software development lifecycle in use