A bicycle-share dock model writes polished test cases for a paid highway transponder program the city does not operate. Which quality metric is most clearly failing?
Select an answer to reveal the explanation.
Short Explanation
Pretty cases for the wrong product fail relevance. If it isn’t in the test basis or domain, it doesn’t fit—even if it reads well.
Full Explanation
When a bicycle-share dock model writes polished test cases for a paid highway transponder program the city does not operate, the quality metric most clearly failing is relevance and contextual fit—outputs applicable and consistent with the test basis and domain requirements. Civic micromobility QA cannot accept beautiful cases aimed at the wrong public service. Measuring execution success only by compiler version numbers fails as an unrelated toolchain detail. Redefining precision as adjective count in titles fails to capture false topical drift. Citing neuron coverage of a traffic-prediction model fails by concept relative to testware relevance for dock kiosks. Exam caveat: relevance asks whether outputs belong to this basis and domain, not whether they sound professional. Operational check: reject transponder cases as out-of-scope, re-prompt with dock wireframes and city bike policies, and score the next civic pack for contextual fit before automation translation. 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.