A public-wifi guest-voucher story says vouchers “expire soon” with no clock, duration, or timezone. Which GenAI analysis ask should the tester choose next?
Select an answer to reveal the explanation.
Short Explanation
“Expire soon” is a foggy street sign—useful intent, missing numbers. The next GenAI analysis ask should hunt ambiguities and gaps in the test basis before anyone scripts clicks. Clarify the clock first; automate later.
Full Explanation
When a public-wifi guest-voucher story says vouchers “expire soon” without a clock, duration, or timezone, the appropriate next GenAI analysis ask is a prompt that identifies inconsistencies, ambiguities, or incomplete information in the test basis. Civic guest-access programs cannot fairly enforce expiration without measurable criteria, so analysis must surface those gaps before design or automation hardens fog into false precision. Jumping immediately to a full UI automation script for voucher login fails because scripting assumes a clarified basis and skips the ambiguity hunt that protects public users from arbitrary cutoffs. Measuring metamorphic relations while treating the LLM as the system under test fails by concept: that is model-evaluation technique selection, not test-basis analysis of a municipal wifi story. Asking only for a CI dashboard layout with no story review fails because build dashboards do not resolve missing expiration semantics in requirements. Exam caveat: analysis prompts should match the defect in the basis—here incompleteness—before generation or tooling prompts. Operational check: prompt GenAI to list ambiguities in the voucher story, confirm timezone and duration with the network steward, update the civic acceptance criteria, and only then authorize automation against the clarified expiry rule.