Our inspection parser's mock returns true to every method while the controller is unavailable. The screen looks successful without checking much. I want version-linked response tests and clear limits, not a claim that this boolean substitute models the robot. Where should the small test set begin?
Make unsupported calls fail clearly, then feed documented success and failure replies through the real adapter. Otherwise a richer-looking substitute can still hide a misspelled method before the parser even sees a response.
It does accept arbitrary method names now. I have one captured success and one failure, but need to recover their SDK version before using them as contract examples.
I would keep the captures as evidence while that version is checked, rather than assign them to whichever SDK is currently installed; a real response can still be the wrong reference for the interface you intend to support.
Does the current display distinguish a missing reading from an actual inspection failure? A reassuring default and an invented reject can both mislead the person looking at the result.
We have no-current-reading, request failure and valid inspection outcome in the proposed display states. The saved report currently collapses the first two, so that is another place to check.
Ada's question is the important one there. A request can succeed and return a genuine failed inspection; don't make the adapter treat every negative-looking value as unavailable.
And test a good read followed by malformed data, Clara, because a parser can return the correct error while the old display state stays in place and tells the operator something else.
The developer recovered the capture version. We now have explicit method checks and separate request-success and inspection-outcome interpretation in the offline adapter; malformed replies are still to add.
Application maintainer is checking the cases against the documented interface, and quality is reviewing how valid inspection outcomes appear. We are not using current output as its own authority.
Both are in scope. The valid failed-inspection case is now displayed and recorded distinctly from request failure. This establishes those software cases, not the physical inspection's accuracy.
Not yet, Ada. Malformed and timing cases remain open. We have a bounded set of call and interpretation checks, with those limits written beside the test results.