Our offline fixture-status screen has never met a response it dislikes, because the mock returns true regardless of what the real query would return; I want to give the developer a small set of saved responses from the documented interface, including an unreadable result, and check the actual screen rather than pretend we have simulated the workshop. What cases would you begin with?
How should I test UR5e fixture status without an always-true mock?
AishaAllen0344 · 9 Mar 2026, 16:19 UTC
0 replies
Discussion closed
This discussion is closed to new replies after six months without activity. Last activity: .