I removed the status read from our offline UR5e report test. Still green. Apparently the substitute's constant true is doing everyone's homework.
Our UR5e test stays green when I remove the status read
PriyaBarnes0568 · 2025年12月26日 16:22 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
8 条回复
What is the test asserting about the report, rather than the substitute: does it inspect the displayed status and failure state?
20分Only that the page opens. No check of which query was called or what the report contains.
2分Then start with one real reporting question. I would rather see one failed read handled correctly than a pretend controller which smiles at every method you invent.
10分For that one read, can the developer restrict the method and arguments to the documented version, then test representative valid, failed and malformed responses?
3分Will the same tests check what appears when the first request fails and there is no previous reading?
7分Included now. Wrong calls fail, malformed responses are rejected, and the first failed read shows unavailable.
4分Useful progress. Keep the installed comparison on the handover list, though; the workshop being unavailable hasn't turned the substitute into the workshop.
5分Did they also try a valid read followed by a failure, with the old value visibly identified as old?
10分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .