Commitment 6:
Test completeness
The purpose of testing is to confirm ability to operate in the intended
environment for the intended results and the thoroughness, which will be
monitored by means of recognised measurement techniques such as test
coverage.
During the early stages of testing (unit and To achieve objectivity we will cross reference
module) we will design tests to exercise as functionality as defined in the source
many of the software paths as is practical in specification against the elements of the test
order to identify anomalies in coding and specification.
design. Completeness of this activity will be
measured by means of statement, decision, Realistic or representative data and
and related forms of coverage analysis. Any environment is key to a comprehensive testing
gaps in coverage will be explained and justified. programme.
During the later stages, when integrating We recognise that requirements may evolve
modules and subsystems, we will ensure that over the testing cycle. We will take the
the integration tests cover the full range of necessary steps to regularly review the test
capabilities of the integrated set of modules. programme for continued sufficiency and
We will review the test results and the currency.
decisions made on the basis of those results
before progressing beyond the integration
stage.
8 Intellect Software Testing Code of Best Practice
Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12