简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

Our FR10 mock accepts a method the application misspells

LucyBrown0915 · 2026年4月3日 10:59 UTC

回复讨论
LU
LucyBrown0915
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.

5 条回复

NO
NoraAli0235

Make unknown methods fail. Does it also accept any arguments?

10
LU
LucyBrown0915

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
NO
NoraAli0235

Include a failed request containing numeric data. Don't let the parser discover a convenient success value.

12
LU
LucyBrown0915

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
NO
NoraAli0235

Useful. Keep the old permissive fake out of the test imports.

6

参与讨论

欢迎来到 Application Robot

所有人都可以阅读论坛。登录或注册后即可发起讨论、回复或上传照片。

忘记密码?

注册账号即表示你同意我们的 使用条款 社区准则。请阅读我们的 隐私政策 ,了解我们如何处理你的信息。