A botanical-garden pest identifier started as an exploratory pilot. Requirements are still thin and keep moving. Why is the oracle hard?
Select an answer to reveal the explanation.
Short Explanation
A pest identifier still in an exploratory pilot, with thin requirements that keep moving, leaves testers without a stable expected-result table. Incomplete or evolving specs are why the oracle is hard. A thin spec does not already name every expected pest label.
Full Explanation
Exploratory AI development and missing or incomplete specs create the test-oracle problem. Claiming the spec is already complete, substituting Chapter 5, or turning the item into an implementation task misses that reason.