Information Technology Reference
In-Depth Information
Figure 12.1b
Analysis of first-week test execution outcomes
12.3 DEFECT DISCOVERY FOCUSING ON
INDIVIDUAL DEFECTS
As we saw in the previous section, there are several possible reasons why the
execution of a test case can be considered unsuccessful. The remaining sections of
this chapter use the term “defect” for a confi rmed software error discovered by test
execution and requiring correction.
At its most basic level, testing discovers defects one at a time. Once the defect
has been corrected and retested, the particular area of software under test may
operate defect free throughout the remaining test case execution. More frequently,
the correction of one defect simply allows the test case to proceed to the next de-
fect in the software, resulting in a number of discovery/correction cycles that are
required before the test case can run to successful completion. It is also likely that
multiple test cases with different testing objectives in the same area of the software
will discover different sequences of defects. The implication is that a single suc-
cessful test case does not guarantee defect-free code in the area of the software
being tested.
The incremental discovery and correction retesting of software defects is
the primary way that software testers help software developers implement the
development requirements. The fewer the latent defects in the delivered software,
the closer the software comes to fulfi lling the requirements. The success of in-
cremental defect discovery is directly related to the management process used
to track defects from discovery to correction. If defects are discovered but not
reported to developers, then testing provides no real value to the development
effort. If the defects are discovered and reported to developers but the corrective
Search WWH ::




Custom Search