New testers at a municipal no-mow-May desk still write only “make tests” after the intro class. What official skill-progression line should cultivation follow?
Select an answer to reveal the explanation.
Short Explanation
First learn to write a clear ask, then sharpen it into test-shaped prompts. Cultivation moves from basic prompt creation to focused, test-specific prompts. Vague “make tests” is the starting line, not the finish.
Full Explanation
Skill cultivation progresses members from basic prompt creation toward more focused, test-specific prompts. New testers at a municipal no-mow-May desk who still write only “make tests” after the intro class need that progression toward precise, test-oriented asks. Jumping immediately from no prompts to autonomous multi-agent orchestration skips foundational craft. Staying forever on one generic prompt template with no test focus freezes skill growth. Replacing prompt skill with only GUI clicking in an LLM-powered tool abandons prompt craft the syllabus still values. Exam caveat: skipping straight to complex agent setups, freezing on generic wording, or abandoning prompt craft for tool clicking alone misses that progression. Operational check: coach no-mow-May newcomers from “make tests” to focused prompts that name objectives, format, and constraints for civic cases. Keep civic testware subject to the same review discipline you would apply to human-authored packs. On the written exam, prefer syllabus terminology over vendor marketing language or lab choreography. Treat fluent output as a draft until organizational quality gates and data-handling rules are satisfied. Align the choice with GenAI-for-testing strategy rather than with CT-AI model-as-SUT measurement unless the stem asks for that lane.