Our offline inspection parser passes when I misspell the status query. The substitute interface accepts any method and returns true, so the screen is delighted with nonsense.
The UR5e cell is unavailable. I want a test that can fail honestly, starting with this one documented read.
Restrict the substitute to that documented method and its arguments, using the interface version your application targets; what response does the parser actually expect beyond a successful call?
Test the parser with representative version-linked responses, including failures and malformed content, and check the displayed result; rejecting the misspelled method is a useful first check but leaves that skipped path unanswered
Our software check once compared only whether a window opened. Could you deliberately damage one expected field and show that the test fails for the intended reason? I would find that easier to trust than another green summary.
Did the revised test exercise the parser, Naomi, including the first request failing before any valid status exists? An old successful value can hide that case.
Yes. Wrong method and malformed fields now fail explicitly; an initial failed read displays unavailable. The old substitute is removed from these tests. Comparison with the installed interface is still outstanding.