Our UR5e inspection cell is reserved for commissioning, so I am developing the fixture-status application offline. The substitute returns true to every method and keeps the screen agreeable. I need a response contract test that can expose bad interpretation; no claim that an inspection block or physical cell is being simulated.
Make the substitute answer the documented calls with versioned examples of success, failure and unexpected data, through the same adapter the real application uses. Reject unsupported calls instead of inventing success. Then check the display after a failed read; a correct parser is little comfort if yesterday's healthy fixture state stays looking current.
The contract-based substitute exposed a failure response being treated as a valid fixture state. That branch is fixed and covered by the captured-shape test; unavailable now reaches the screen. We still need the supported read-only comparison when the real cell becomes available. This is software evidence only.