The reporting screen passes its offline tests even with a misspelled SDK call. Our fake invents any requested method and returns true. Handy for a screenshot, useless for checking the wrapper. I want the read-only reporting tests tied to our actual SDK version and response shapes.
Yep. I replaced that bit with explicit methods and checked signatures against the version we use. The typo now fails. So does a caller sending the wrong argument name. Response handling is next.
Tests now cover the documented success shape, request failure, missing data and a timeout. Failure carrying numeric details no longer populates the status tile. I also made an unexpected shape show unavailable instead of retaining a fresh-looking value. Those tests and the call-contract tests pass.