Our cell is unavailable, so I'm working offline on inspection result parsing for Fairino FR5 in a maintenance setup with documented status queries, with a sample bracket as a reference.
The existing SDK mock returns true from every method.
The screen looks happy, but that doesn't catch interface mistakes.
I want a useful software substitute without claiming it simulates the physical robot.
Do you've captured success and error responses tied to the documentation for the SDK your screen uses? Those would give the substitute concrete contracts to follow.
Use a small substitute implementing only your required methods, matching the saved response contracts and rejecting unexpected calls. That should keep the run contained offline.
Rejecting unknown mock methods doesn't establish that the application stays offline. Another startup path could still create the real controller client.
You're right. I blurred two checks. The strict interface catches wrong calls; offline startup also needs to exclude the real client and reject controller endpoint configuration.
Yes, treat that as an explicit offline failure. It identifies an unsupported method or unwanted application call and should never trigger controller access.
My substitute accepted arbitrary method names. A typo passed every offline run. The fake was exceptionally supportive and entirely useless for that mistake.
@RebeccaArcher0430 The saved error reproduces our parser bug offline, so the substitute has a useful starting point. I haven't completed the interface and offline-boundary checks.