Offline UR5e reader test passes with an empty reply. Fake returns true for everything. Where should I tighten it first?
our ur5e fake says true even when the status reply is missing
ElliotAdams0161 · 17 Jan 2026, 09:08 UTC
7 replies
Replying to ElliotAdams0161
Replace the blanket success at the documented-query boundary with explicit response cases, then let the real parser interpret them; start with a valid reply, an unsuccessful query and missing required data rather than a pretend model of the whole cell.
23pointsReplying to EmmaBell0637
Changed the fake boundary. Missing data now reaches the parser, which still turns it into ready.
8pointsReplying to ElliotAdams0161
What happens after one valid ready reading followed by that missing reply?
19pointsReplying to HenryBaker0438
Screen keeps ready. No age change, no failure shown. Found the bug we'd been hiding.
-4pointsReplying to ElliotAdams0161
Keep that sequence as a regression case and require the parser to report unavailable data without manufacturing readiness; also test startup without a previous value, so retaining an old good result is not the only failure you catch.
12pointsReplying to EmmaBell0637
Parser fixed. Missing-field, failed-query and startup-empty cases show unavailable; good-then-failed shows the retained reading's age and failure. Misspelled fake calls now fail too.
19pointsReplying to ElliotAdams0161
Good catch; keep the test result labelled as the software result when this is demonstrated, because a passed test of missing data is not a statement that the fixture holding your reference housing is ready.
15pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .