5.5 Defect Management

Question 1

Since one of the major test objectives is to find defects, an established …

Answer 1

defect management process is essential.

Question 2

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 …

Answer 2

real defects or something else

dealing with the defect reports.

Question 3

Anomalies may be reported during any phase of the SDLC …

Answer 3

and the form depends on the SDLC.

Question 4

At a minimum, the defect management process includes a workflow for handling individual defects or anomalies from their discovery …

Answer 4

to their closure and rules for their classification.

Question 5

The workflow typically comprises activities to:
- log the …
- analyze and …
- decide on a suitable response such as …
- to close the

Answer 5

• reported anomalies
• classify them
• to fix or keep it as it is
• defect report.

Question 6

The process must be followed by …

Answer 6

all involved stakeholders.

Question 7

It is advisable to handle defects from … in a …

Answer 7

static testing (especially static analysis)

similar way.

Question 8

Typical defect reports have the following objectives:
- provide those responsible for handling and resolving reported defects …
- provide a means of tracking …
- provides ideas for improvement of …

Answer 8

• with sufficient information to resolve the issue
• the quality of the work product
• the development and test process

Question 9

A defect report logged during dynamic testing typically includes:
- unique …
- title with a short …
- date when the anomaly was observed, i…
- identification of the …
- context of the defect (e.g. test case being run, test activity being performed, SDLC phase, and …
- description of the failure to enable reproduction and resolution including the test strips that detected the anomaly, and any relevant …
- expected results and …
- severity of the defect … on the interests of …
- priority
- status of the defect (e.g open, deferred, duplicate, waiting to be fixed, awaiting …
- references

Answer 9

• identifier
• summary of the anomaly being reported
• issuing organization, author and their role
• test object and test environment
• other relevant data like the test technique, checklist, or test data being used)
• test logs, database dumps, screenshots, or recording
• actual results
• (degree of impact)
  stakeholders or requirements
• to fix
• confirmation testing, re-opened, closed, rejected)
• (e.g. to the test case)

Question 10

Some of this data may be automatically included when using ..

Answer 10

defect management tools (e.g. identifier, date, author and initial status).

Question 11

Document templates for a defect report and example defect reports can be found in the …

Answer 11

ISO/IEC/IEEE 29119-3 standard, which refers to defect reports as incident reports.