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.
Our FR10 mock accepts a method the application misspells
LucyBrown0915 · 3 Apr 2026, 10:59 UTC
5 replies
Replying to LucyBrown0915
Make unknown methods fail. Does it also accept any arguments?
10pointsReplying to NoraAli0235
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.
1pointsReplying to LucyBrown0915
Include a failed request containing numeric data. Don't let the parser discover a convenient success value.
12pointsReplying to NoraAli0235
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.
9pointsReplying to LucyBrown0915
Useful. Keep the old permissive fake out of the test imports.
6pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .