I commented out the parser while tracking a display problem and the offline tests still passed. Our SDK fake returns true, then the screen uses its default values. So we have tested a very convincing empty report. What should the first replacement test actually assert?
Assert the interpreted fields from a documented response for your installed interface version, not just that the screen opens. Then include a documented failed reply and malformed data. Does your wrapper currently invent a value when a required field is absent?
Yes, it supplies available when parsing gives nothing back. Programmer has removed that default in the test version. We now check the parsed fields and unavailable state separately, though the old-value-after-failure case still needs work.
Did that remaining case get fixed? Include starting with a failed request too. Otherwise the report can learn to label an old value correctly while still inventing the first one when no reading ever succeeded.