A robotics project's mock robot now runs through the same hardware execution path used for Franka and UR5e industrial robot arms. A hardware configuration selects the robot, timing interval, and maximum step count, while a latency monitor and the normal completion check stay in the path. Three integration tests bring the project total from 98 to 101.
Mocks often bypass the exact code that fails on a machine. This one enters through the production configuration, runs a complete episode, and returns the residual error between hardware and simulation for calibration. An engineer can therefore catch a missing field, bad stop condition, or broken result shape on a laptop, before booking a robot and discovering the setup won't start.
The mock cannot reveal a loose cable, motor timing jitter, or a wrong physical calibration. It does reserve the real machine for those physical questions. If the new tests stay aligned with each supported robot configuration, routine software failures should stop consuming robot time during bring-up.