ISTQB Defect Management Process 4

Question 1

A defect is found in a module that was recently changed. In ISTQB terminology, this type of defect introduced by a change is called a:

Accepted Answer

Regression defect

Answer

A regression defect is one introduced by a change (code fix, new feature, or configuration change) that inadvertently breaks previously working functionality.

Question 2

During defect reporting, why should a tester avoid including the proposed fix in the defect report?

Accepted Answer

Proposing fixes is outside the tester's role; defect reports should describe problems, not solutions

Answer

Defect reports should objectively describe the problem; suggesting fixes can bias developers and is beyond the tester's responsibility in most processes.

Question 3

What does 'severity' measure in the context of ISTQB defect management?

Accepted Answer

The degree of impact the defect has on the system or component under test

Answer

Severity reflects the technical impact on the system's functionality, distinguishing it from priority which reflects business urgency.

Question 4

A 'blocker' severity defect is reported. What does this typically mean for the test cycle?

Accepted Answer

Testing of the affected area or the entire build cannot proceed until the defect is resolved

Answer

A blocker prevents testing from continuing in the affected area, often halting the entire test cycle until it is fixed.

Question 5

Which of the following is a key benefit of using a dedicated defect tracking tool rather than a spreadsheet?

Accepted Answer

It provides workflow enforcement, audit trails, and reporting metrics automatically

Answer

Defect tracking tools enforce lifecycle workflows, maintain full audit trails, and generate metrics that spreadsheets cannot reliably provide.

ISTQB - International Software Testing Qualifications Board Practice Test

ISTQB - International Software Testing Qualifications Board Practice Test

ISTQB Defect Management Process 4