Controller's unavailable, so I'm testing inspection parsing offline. Every mock method returns true. How do I make this catch an actual interface mistake instead of applauding every screen?
our FR10 mock says yes to absolutely everything
BethArcher0411 · 2025年7月28日 01:44 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
4 条回复
A substitute that always succeeds can hide the same problems as an incomplete inspection checklist. Use the documented return shapes for the version you're targeting, plus failures and malformed replies. Keep this about software behaviour, not simulated robot performance.
14分Found one already: screen treats any nonempty container as success. I'm adding the documented failure shape, then a good response followed by failure so stale values don't sneak through.
-2分Also make unexpected calls fail visibly in the mock. Otherwise a misspelled method or wrong argument list can still get a cheerful true without exercising the interface you meant to use.
10分Will you check the revised display with its users as well? A technically correct unknown state still needs to be distinguishable from a fresh inspection result.
11分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .