A community flour-share desk asks what new daily work testers take on when GenAI enters testing. Which expanded task set is recognized?
Select an answer to reveal the explanation.
Short Explanation
New chores show up beside classic testing: review what AI produced, sharpen the prompts, and keep the test-specific prompt library healthy. That trio is the expanded daily work—not generate-and-forget.
Full Explanation
When GenAI enters testing, recognized expanded daily work for testers includes review of overall AI-based output, prompt refinement, and maintenance of test-specific prompt libraries. A community flour-share desk asking what new daily work testers take on should land on that set rather than on generate-and-ignore behavior. Only clicking generate and never reading the output abandons review. Only purchasing vendor licenses with no review duty is procurement, not tester work. Only red-teaming the LLM as the product under test is CT-AI SUT focus, not GenAI-for-testing task expansion. Exam caveat: review, refine, and maintain prompt libraries are the expanded tasks; SUT red-teaming is a different syllabus lane. Operational check: add flour-share calendar time for output review, prompt refinement, and upkeep of the test-specific prompt library. 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.