The cell is unavailable, so I'm testing inspection-result parsing offline. Our mock returns true for everything. Even a misspelled call keeps the screen happy. What should this substitute actually check?
Start with the documented interface for the version you're using. The substitute should reject unknown methods and wrong arguments, and return representative success and failure shapes rather than one universal true. Keep that separate from any claim about robot motion
Thanks Aisha. I can get the installed version and recorded query returns. We only need this to test the parser and screen, not to imitate the physical cell.
Add explicit expected screen states for those recorded returns. Otherwise the mock may become more realistic while the test still checks only that the page renders.
And check what happens after a valid result followed by a failed request. I mean the screen shouldn't quietly keep the old result looking current just because the failure case itself no longer crashes
That case caught another gap. The old result stays visible with no age or failure indication. I've added a separate expected unavailable state to the screen review.
Keep the original typo as a failing interface test after the replacement is written. It is a useful small check that the new substitute hasn't accidentally become permissive again