I am testing our status display while the FR10 bench is unavailable. The substitute returns true for every call, so an error path can be broken without any test noticing. I need representative successful, failed and malformed responses at the software boundary, rather than a screen that is permanently satisfied.
Our offline FR10 substitute approves every status request
FarahBennett0765 · 2025年7月30日 01:20 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
1 条回复
Start with the few response shapes the display actually consumes, using the documented interface and saved examples from your version; I'd make one request fail after a good reading too, because an old green value can look wonderfully healthy
14分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .