How can our FR5 reporting mock expose a wrong interface?

SaraAdams0113 · 16 Aug 2026, 02:54 UTC

Reply to discussion
SA
SaraAdams0113
I need offline software-response tests while the FR5 cell is unavailable. Our mock returns true from everything. What should replace that blanket success without claiming physical simulation?

1 reply

ME
MeiBrown0951
Replying to SaraAdams0113

I'd start by having the maintainer identify the supported interface version and the small set of calls your report actually uses. Make wrong calls fail, then use sourced response examples for normal, negative and failed reads. Keep malformed cases labelled as deliberate test inputs; the screen should be checked as well as the decoder, particularly after it has already shown a good reading.

19 points

Add to the discussion

Welcome to Application Robot

Everyone can read the forum. Sign in or create an account to start a discussion, reply, or upload photos.

Forgot your password?

By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.