CTAL-TAE · Question #108
Which of the following attributes should NOT be included in a test execution report associated with a suite of automated tests?
The correct answer is A. Summary of the test execution results. Option A should NOT be in a test execution report because a summary of results belongs in a Test Summary Report - a separate, higher-level management artifact. A test execution report captures the granular, raw details of what ran, when, where, and what happened; summarizing…
Question
Which of the following attributes should NOT be included in a test execution report associated with a suite of automated tests?
Options
- ASummary of the test execution results
- BSystem/Application under test and its version
- CDefect clusters identified during test execution
- DEnvironment in which the tests have been executed
How the community answered
(33 responses)- A88% (29)
- B3% (1)
- C6% (2)
- D3% (1)
Explanation
Option A should NOT be in a test execution report because a summary of results belongs in a Test Summary Report - a separate, higher-level management artifact. A test execution report captures the granular, raw details of what ran, when, where, and what happened; summarizing those results is the job of a different document.
Why the distractors are wrong (i.e., they SHOULD be included):
- B - The system/application version is essential for traceability and reproducibility; without it, you can't link failures to a specific build.
- C - Defect clusters observed during execution belong in the report because they provide immediate risk intelligence to the team.
- D - The environment (OS, browser, hardware, config) is critical context; the same test can pass in one environment and fail in another.
Memory tip: Think of a test execution report as a flight data recorder - it logs raw facts (what ran, on what, under what conditions, with what outcome). A "summary" is the pilot's debrief - that's a different document entirely.
Topics
Community Discussion
No community discussion yet for this question.