A garden-plot map wireframe shows a disabled “Waitlist” control that the user story never mentions. Why would a tester feed both the wireframe image and the story into a multimodal model when drafting cases?
Select an answer to reveal the explanation.
Short Explanation
Stories do not always name every control the wireframe shows—like a quiet Waitlist button sitting disabled on the map. Image plus story lets the draft catch that extra visual condition. Text-only prompts would happily ignore what they never see.
Full Explanation
Combining image and story inputs can surface test conditions present in the UI design but absent from written requirements. That improves case coverage of visible controls such as a disabled Waitlist element. Multimodal drafting remains support for the tester; it does not redefine the model as the SUT or remove human review.