FR10 reporting mock bypasses the response we need to test

The developer has saved successful and failed reads from the same application version. We can also supply a deliberately incomplete response. The current mock was bypassing the parser entirely.

What does the ordinary screen show after a successful read followed by a failure, Mina?

Keep response failure distinct from the controller status being reported. I would want the screen to say that the read failed, with any older value clearly identified as old.

And test that sequence without clearing the screen between cases, because a fresh screen is very good at hiding yesterday's green value.

Robin, it keeps the old value looking current. The success-to-failure test exposed that immediately. The developer has separated last successful value from current read state in the draft.

Check first-read failure as well. There is no older value to display in that case.

Does incomplete data take the same failure route rather than becoming a false status value?

Yes, and the diagnostic says which required field was absent. First-read failure shows no value. A later failure shows the last reading as old, with its observation time, not as a new reading.

Have the trainer read both screen states without the developer explaining them. The distinction may be correct internally while the wording still suggests an inspection rejection.

The trainer recognised both as unavailable current status, not rejected brackets. Saved success, failed read, incomplete response and success-then-failure all passed through the real reporting screen. This offline repair is complete; controller connection checks remain separate.