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 · 2026年4月3日 10:59 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
5 条回复
Make unknown methods fail. Does it also accept any arguments?
10分回复 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.
1分Include a failed request containing numeric data. Don't let the parser discover a convenient success value.
12分回复 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.
9分Useful. Keep the old permissive fake out of the test imports.
6分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .