A pharmacy agent's tests pass whenever any reply comes back to a symptom question. Pharmacists require that the agent not recommend a dose. What should the test suite add?
Select an answer to reveal the explanation.
Short Explanation
A spell checker that only asks whether ink hit the page will pass a dangerous note. You add a test that fails when the reply recommends a dose, even if the sentences are fluent and polite. A tone check does not catch that line.
Full Explanation
Task-level tests have to encode the constraint the business actually cares about, not only the fact that tokens came back. Pharmacists have said the agent must not recommend a dose, and the current suite passes any reply, so the suite needs a check that fails a fluent answer when it names a dose. Another check that the reply uses a polite tone and a complete sentence rewards courtesy and still passes a dose. A latency check that fails the run when the reply takes longer than the last build measures speed, which is a different defect and can pass a fast unsafe answer. A length check that passes any reply containing more than a few words of advice makes a longer dose recommendation look healthier than a short refusal. Exam caveat: this check is about the content boundary, not about whether the agent may explain how to reach a pharmacist. A reply can be helpful and still contain no dose. Operational check: add a case whose reply names a dose and confirm the suite fails it, then add a case that tells the person to speak with the pharmacist and confirm that case passes.