A museum audio-guide checkout tester attaches a GUI wireframe and a…

Question

A museum audio-guide checkout tester attaches a GUI wireframe and a snippet of the checkout function. A colleague argues those attachments are “context,” not input. Where do screenshots and code belong in the six-component structure?

Accepted Answer

Input data — screenshots, code, existing cases, and output examples are artefacts the model must use; context remains the background that orients test conditions — Think of context as the museum setting and input data as the exhibits you hand over. Wireframes and code are artefacts to use, so they sit under input data. Context still orients what you are testing.

Answer

Context — any visual or code attachment is background, never input data

Answer

Output format — wireframes define how the model must format its reply

Answer

Constraints — code snippets restrict which browsers may be mentioned

A museum audio-guide checkout tester attaches a GUI wireframe and a snippet of the checkout function. A colleague argues those attachments are “context,” not input. Where do screenshots and code belong in the six-component structure?

Short Explanation

Full Explanation