Requirements-Based Testing CT-AUT Practice Questions (Page 5)

Questions 21–25

1. 21foundation · easy

   Which principle is fundamental to requirements-based testing in the automotive context?

   • ATest cases should be designed independently of the requirements to avoid bias.
   • BTesting is complete when all test cases have been executed successfully.
   • CTesting should focus only on functional requirements, ignoring non-functional ones.
   • DEach test case must be traceable to at least one specific requirement.
   Reveal Solution Discussion Select an answer first
2. 22expert · hard

   A test team is working on a parking assist system. The requirements document contains two statements: 'The system shall detect obstacles within 1 meter of the vehicle' and 'The system shall detect obstacles within 0.5 meters of the vehicle.' The test lead must decide how to proceed. What is the best approach?

   • ADesign tests for both ranges and report which ones fail.
   • BAssume the 1-meter range is correct because it is more conservative.
   • CCombine the requirements into a single test that checks detection at both 0.5 and 1 meter.
   • DFlag the conflicting requirements to the requirements owner and ask for clarification before designing tests.
   Reveal Solution Discussion Select an answer first
4. 23expert · hard

   A test engineer is designing tests for an advanced driver assistance system. The requirement states: 'The system shall warn the driver when a pedestrian is detected in the vehicle's path.' The engineer notices that 'vehicle's path' is not defined, and there is no specification for the warning type. The project is in the final stages, and the requirements owner is unavailable for a week. What is the best course of action?

   • AIgnore the ambiguity and design tests based on common sense.
   • BDocument the ambiguity, design tests based on the most reasonable interpretation, and flag the assumption for review when the owner returns.
   • CDelay all test design until the requirements owner clarifies the ambiguity.
   • DDesign tests that cover every possible interpretation of 'vehicle's path' and warning type.
   Reveal Solution Discussion Select an answer first
5. 24foundation · easy

   What should a tester do when they identify an ambiguous requirement during test design?

   • ADocument the ambiguity and clarify it with the requirements owner before writing test cases.
   • BWrite test cases that cover all possible interpretations of the requirement.
   • CSkip testing that requirement until the ambiguity is resolved.
   • DMake an assumption and proceed with test design based on that assumption.
   Reveal Solution Discussion Select an answer first
6. 25foundation · easy

   When deriving test cases from a functional requirement, what is the primary source of information?

   • AThe system architecture documentation.
   • BThe test team's previous experience with similar systems.
   • CThe source code of the software under test.
   • DThe requirement specification itself, including its inputs, expected outputs, and behavior.
   Reveal Solution Discussion Select an answer first