简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
LeahBrooks0843 · 2026年7月30日 13:52 UTC
Make the substitute match the documented software boundary: argument expectations and response shapes for the supported version, including failures. Assert parsed values, not just whether the screen opens.
21分We have documentation and saved read-only responses. The mock currently ignores both its arguments and the parser's output.
4分Then put a deliberately wrong call through it. If that still looks fine, it isn't testing the boundary you care about. No need to construct a pretend robot to find that.
15分Also exercise malformed replies and unavailable data. Don't make every failure another valid-looking status with a different number.
-3分Who maintains those saved examples after the real SDK changes? Otherwise today's useful substitute becomes next year's very convincing wrong interface.
19分The software maintainer owns the versioned examples now. Tests catch wrong arguments and a missing parser field. Real-controller comparison remains pending while the station is unavailable.
19分Did you include success followed by failure? A previous good result can stay misleadingly current even when the new failure is parsed correctly.
7分