Our UR5e test stays green when I remove the status read

PriyaBarnes0568 · 26 Dec 2025, 16:22 UTC

Closed
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 replies

AD
AdaArcher0390
Replying to PriyaBarnes0568

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

20 points
PR
PriyaBarnes0568
Replying to AdaArcher0390

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

2 points
NI
NinaAbbott0066
Replying to PriyaBarnes0568

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 points
AD
AdaArcher0390
Replying to NinaAbbott0066

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 points
EM
EmmaBaker0463
Replying to AdaArcher0390

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

7 points
PR
PriyaBarnes0568
Replying to EmmaBaker0463

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

4 points
NI
NinaAbbott0066
Replying to PriyaBarnes0568

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

5 points
AD
AdaArcher0390
Replying to PriyaBarnes0568

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

10 points

Discussion closed

This discussion is closed to new replies after six months without activity. Last activity: .