our offline status display is always cheerful

I am reviewing a UR5e fixture-status application while the equipment is unavailable. Its mock returns true for every call. The screen says connected and ready even when the requested field does not exist. I want representative recorded responses, missing fields and communication failures tested against the software interface. No motion model needed. How would you organise those cases so the next maintainer can tell which response each test represents?