A city-park picnic-permit pack scores well on execution success rate but poorly on diversity. What should the tester’s next refinement prioritize?
Select an answer to reveal the explanation.
Short Explanation
Scripts run, but they all look the same—so chase diversity next, not prettier headers. Let the weak metric pick the refinement.
Full Explanation
When a city-park picnic-permit pack scores well on execution success rate but poorly on diversity, the tester’s next refinement should prioritize targeting edge-case wording and related refinement techniques because the weak named metric is diversity. Civic park permitting must exercise rain dates, group sizes, and odd clocks—not only runnable happy clones. Only restyling table headers because execution success looks good fails to address the weak metric. Ignoring diversity and declaring the pack finished fails public risk coverage. Switching the entire effort to jailbreak testing of a park chatbot fails by scope. Exam caveat: refine against the failing metric; strong execution success does not excuse weak diversity. Operational check: list under-represented picnic-permit edges, amend prompts for those civic variants, regenerate, re-score diversity while holding execution success, and stop only when both gates meet parks QA thresholds. Retain the municipal audit note so later testers can see why the decision protects public service quality and fairness. Retain the municipal audit note so later testers can see why the decision protects public service quality and fairness. Retain the municipal audit note so later testers can see why the decision protects public service quality and fairness.