A public-radio pledge script is syntactically tidy; when run against the pledge form it clicks a control that is not on the page. Which detection approach revealed the defect?
Select an answer to reveal the explanation.
Short Explanation
Pretty code that clicks a missing button still fails in the real world. Running the generated script against the form is output testing.
Full Explanation
When a public-radio pledge script is syntactically tidy but, when run against the pledge form, clicks a control that is not on the page, the detection approach that revealed the defect is output testing by executing the generated script against the test object. Civic fundraising automation must prove runtime fit to the real form, not stop at desk review. Tone-checking for professional wording fails to find missing controls. Counting tokens in the prompt to estimate quality fails as a proxy unrelated to executability on the object. Metamorphic testing of the underlying language model fails by concept when the revelation came from running application scripts. Exam caveat: output testing executes artefacts against the SUT/test object. Operational check: run generated civic pledge scripts in a safe test tenant, capture missing-control failures, feed UI inventories back into prompts, and promote only scripts that execute cleanly on the current form. 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.