简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

Our UR5e test stays green when I remove the status read

PriyaBarnes0568 · 2025年12月26日 16:22 UTC

已关闭
PR
PriyaBarnes0568
I removed the status read from our offline UR5e report test. Still green. Apparently the substitute's constant true is doing everyone's homework.

8 条回复

AD
AdaArcher0390

What is the test asserting about the report, rather than the substitute: does it inspect the displayed status and failure state?

20
PR
PriyaBarnes0568

Only that the page opens. No check of which query was called or what the report contains.

2
NI
NinaAbbott0066

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
AD
AdaArcher0390

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
EM
EmmaBaker0463

Will the same tests check what appears when the first request fails and there is no previous reading?

7
PR
PriyaBarnes0568

Included now. Wrong calls fail, malformed responses are rejected, and the first failed read shows unavailable.

4
NI
NinaAbbott0066

Useful progress. Keep the installed comparison on the handover list, though; the workshop being unavailable hasn't turned the substitute into the workshop.

5
AD
AdaArcher0390

Did they also try a valid read followed by a failure, with the old value visibly identified as old?

10

讨论已关闭

此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .