CTFL_SYLL_4.0 · Question #87
You have just completed a retrospective at the end of a sprint. One of the developers raised an issue with defect reports not containing information about the configuration, data, and system being…
The correct answer is A. Increased test effectiveness / efficiency. Improving the defect report template to include configuration, data, and system details upfront eliminates the costly back-and-forth cycle (3–4 iterations per report), making the testing process faster (efficient) and more reliable (effective) - a direct, measurable improvement…
Question
You have just completed a retrospective at the end of a sprint. One of the developers raised an issue with defect reports not containing information about the configuration, data, and system being used when the failure occurred. When this happens, they reject the defect report and the tester has to update it and send it again. This sometimes takes three or four iterations to get all the information on the report. The test team will take this feedback and will improve the details included in the defect reports. This is an example of which type of benefit for testing?
Options
- AIncreased test effectiveness / efficiency
- BTeam bonding and learning
- CImproved quality of the test basis
- DIncreased quality of the test cases
How the community answered
(50 responses)- A84% (42)
- B8% (4)
- C2% (1)
- D6% (3)
Explanation
Improving the defect report template to include configuration, data, and system details upfront eliminates the costly back-and-forth cycle (3–4 iterations per report), making the testing process faster (efficient) and more reliable (effective) - a direct, measurable improvement to how testing work gets done.
Why the distractors are wrong:
- B (Team bonding and learning): While the retrospective involves collaboration, the outcome here is a process improvement, not a social or learning benefit. Team bonding is about relationships, not report quality.
- C (Improved quality of the test basis): The test basis refers to the source documents used to derive test cases (requirements, specs, designs). Defect reports are outputs of testing, not inputs to test design.
- D (Increased quality of test cases): Test cases define what to test and how. Defect reports document failures found. Fixing a report template does not improve the test cases themselves.
Memory tip: Ask yourself "what is actually getting better here?" - the process of reporting defects takes fewer round-trips, saving time and effort. Anytime a change reduces rework or wasted cycles in testing, think efficiency/effectiveness (A). Reserve C and D for improvements to the inputs (requirements/specs) or tools (test cases) of testing, not the outputs.
Topics
Community Discussion
No community discussion yet for this question.