CAST Test Execution and Reporting 4

Question 1

A defect marked as 'Rejected' or 'Not a Bug' by a developer usually means:

Accepted Answer

The reported behavior matches the intended design or could not be reproduced

Answer

Rejected defects typically reflect expected behavior or an inability to reproduce the issue.

Question 2

What is 'retesting' (confirmation testing)?

Accepted Answer

Re-executing a failed test after the defect is reportedly fixed

Answer

Retesting confirms that a specific defect has actually been resolved.

Question 3

Which report element best communicates testing trends over time?

Accepted Answer

A defect trend chart showing opened vs. closed defects per period

Answer

Defect trend charts visualize how defect discovery and resolution evolve across the cycle.

Question 4

When execution time is limited, which tests should be prioritized?

Accepted Answer

High-risk and high-priority test cases first

Answer

Risk-based prioritization ensures the most important areas are tested when time is constrained.

Question 5

What does a high defect density in a particular module suggest?

Accepted Answer

That module may need additional testing or code review attention

Answer

High defect density flags a risky module that likely warrants deeper investigation.

CAST Test Practice Test