CTAL-TTA_001 · Question #57
Part 7 "Test Process & Incident Management" Which TWO of the following artefacts can be useful as a test oracle the first time a test case is run? 1 credit [K2]
The correct answer is B. Requirements Specification D. Legacy system. A test oracle is any source that provides the expected outcome of a test, allowing you to judge pass/fail. On the first run, you cannot compare against a previous result, so you need an independent reference. B (Requirements Specification) is correct because it explicitly…
Question
Part 7 "Test Process & Incident Management" Which TWO of the following artefacts can be useful as a test oracle the first time a test case is run? 1 credit [K2]
Exhibit
Options
- AIncident report
- BRequirements Specification
- CTest summary report
- DLegacy system
- ETest plan
How the community answered
(33 responses)- A3% (1)
- B88% (29)
- C6% (2)
- E3% (1)
Explanation
A test oracle is any source that provides the expected outcome of a test, allowing you to judge pass/fail. On the first run, you cannot compare against a previous result, so you need an independent reference.
B (Requirements Specification) is correct because it explicitly defines what the system should do - making it a primary oracle for deriving expected results before any test has run.
D (Legacy system) is correct because you can feed the same inputs into the old system and treat its output as the expected result for the new system. This "back-to-back" comparison works from the very first run.
Why the distractors fail:
- A (Incident report) - documents a defect already found; it's an output of testing, not a source of expected results.
- C (Test summary report) - summarises testing outcomes at the end of a cycle; again an output, not an oracle.
- E (Test plan) - describes the approach and scope of testing, not the expected behaviour of the system under test.
Memory tip: Ask yourself "Does this artefact tell me what the system SHOULD produce?" Requirements say what should happen; a legacy system shows what did happen before. Plans and reports describe the testing process itself - they never tell you the expected result.
Topics
Community Discussion
No community discussion yet for this question.
