Clear, complete, and testable requirements or user stories are critical for effective acceptance testing. Ambiguities or vague statements lead to differing interpretations by stakeholders, developers, and testers. This often results in software that doesn’t meet user expectations or in tests that fail to verify business needs correctly.
Option B is correct because it highlights the importance of precise requirements in both implementation and testing phases. Ambiguities can result in incorrect behavior, untestable features, or test cases that don’t align with business goals.
Other options:
A is risky — while testers may explore assumptions during exploratory testing, relying on assumptions rather than clarification increases risk.
C is incorrect — the INVEST mnemonic helps write better user stories, but it doesn’t replace review or validation processes.
D is false — Agile still values requirements engineering; it’s more collaborative and incremental, with the product owner playing a key role, not diminishing its importance.
Answer: B. Vague or ambiguous requirements may lead to misunderstandings both during implementation and testing
