Controller unavailable. Our sample-display mock returns true for everything. How do I test the actual software calls without claiming an inspection trial?
fr5 sample mock accepts calls the real interface may reject
CalebChan1102 · 2026年7月4日 04:40 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
8 条回复
Make the substitute expose the methods and arguments your installed interface supports, with matching response shapes; accepting every call can hide mistakes before the parser even sees a result
9分回复 MeiBell0690
Found a misspelled read method. The mock's generic fallback accepted it; the installed interface does not.
22分Remove that fallback. Unknown calls should fail the test, not produce another reassuring screen.
1分Does the corrected call now exercise the application's normal response parser, or is the fake still handing the display a simplified value?
7分Use retained responses with their version noted for that parser, including unsuccessful reads; detailed method checking and response interpretation are separate bits of software coverage
9分Normal parser now used. Correct and failed saved responses produce the expected display states. The strict substitute also rejects the misspelled method and wrong argument count; tests name those cases. No controller behaviour inferred.
20分Will those strict-interface tests remain in the normal test run when the controller returns, rather than becoming an offline-only tool nobody opens again?
10分Included in the standard run and handover. Controller comparison remains a separate commissioning task.
10分