5.5 Defect Management Flashcards
Since one of the major test objectives is to find defects, an established …
defect management process is essential.
Although we refer to “defects” here, the reported anomalies may turn out to be … (e.g. false-positive result, change request) - this is resolved during the process of …
real defects or something else
dealing with the defect reports.
Anomalies may be reported during any phase of the SDLC and the form …
depends on the SDLC.
At a minimum, the defect management process includes a workflow for handling individual defects or anomalies from their discovery …
to their closure and rules for their classification.
The workflow typically comprises activities to:
- log the …
- analyze and …
- decide on a suitable response such as …
- to close the …
- reported anomalies
- classify them
- to fix or keep it as it is
- defect report.
The process must be followed by …
all involved stakeholders.
It is advisable to handle defects from … in a …
static testing (especially static analysis)
similar way.
Typical defect reports have the following objectives:
- provide those responsible for handling and resolving reported defects with s…
- provide a means of tracking the q…
- provides ideas for improvement of the d…
- sufficient information to resolve the issue
- quality of the work product
- development and test process
A defect report logged during dynamic testing typically includes:
- unique i…
- title with a short “ “ of the a…
- date when the anomaly was observed, i… , “ “ and t…
- identification of the t… and t…
- context of the defect (e.g. test case being run, test activity being performed, SDLC phase, and other relevant “ “ like the t… , “c…“, or t…
- description of the failure to enable reproduction and resolution including the test steps that detected the anomaly, and any relevant t… , d… , “ “ , or “ “
- expected results and a…
- severity of the defect (d… ) on the interests of …
- priority …
- status of the defect (e.g open, deferred, duplicate, waiting to be fixed, awaiting …
- references (e.g. to t…
- identifier
- summary
anomaly being reported - issuing organization, author and their role
- test object and test environment
- information
test technique
checklist
test data being used) - test logs
database dumps
screenshots
recording - actual results
- (degree of impact)
stakeholders or requirements - to fix
- confirmation testing, re-opened, closed, rejected)
- the test case)
Some of this data may be automatically included when using defect m… (e.g. “i…“, “d…“, “a…“, and i…
management tools
identifier
date
author
initial status).
Document templates for a defect report and example defect reports can be found in the ISO/IEC/IEEE 2… which refers d… to as i…
29119-3 standard,
defect reports as incident reports.
