CTAL-TA v4.0: Certified Tester Advanced Level Test AnalystDemo

Question

Your root cause analysis has revealed that most of the defects found in production occurred in areas of the system that received little or no testing. These areas had been treated as low priority by the testing team because there was no expectation that they would ever change. Further investigation showed that these areas actually were changed by developers while they were implementing features in other parts of the system and fixing other defects.

What action can you take to help prevent this situation from recurring in the future?

A Keep the Defect Detection Percentage low
B Conduct a test gap analysis to see if the testing is exercising the areas of the code that have changed
C Look at the defect arrival pattern to target the defect cluster areas and target the testing at those areas
D Analyze the root causes of the defects to determine how the defects were introduced into the system and implement process changes as needed

Explanation

Test gap analysis is a technique that compares the current source code of the system against a previous baseline (e.g., the last release) to identify newly added or changed code, and then cross-references this against actual test execution/coverage data to reveal code that was changed but never exercised by any test. Applying this technique addresses the root cause identified in the scenario — that code areas assumed to be static were in fact modified as a side effect of other development work, and that modification went untested because no one verified whether test coverage still aligned with the current, changed state of the code. By systematically checking whether tests actually exercise changed areas (rather than relying on assumptions about which areas are 'stable'), the team can detect and close such coverage gaps before defects reach production.

Learn more

CTAL-TA v4.0: Certified Tester Advanced Level Test AnalystDemo

AstroTutor

Notes

Readiness

QuestionQ54

Community Discussion