I need my offline FR5 inspection application to cope with responses, not pretend it has moved the inspection block. The training controller is unavailable, and my current fake returns true to every call. That keeps the screen happy while telling me almost nothing about whether I parse a result correctly. Where would you start replacing those blanket successes with useful response cases? I want to keep this firmly a software test, without claiming a physical simulation.
A permanently cheerful mock is hiding my result-parsing errors
RobinBrown0947 · 23 Aug 2026, 06:07 UTC
0 replies
Add to the discussion
Welcome to Application Robot
By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.