testinglisted

# testing The cross-cutting testing umbrella for robium. Robotics apps fail in layers a generic test suite misses — a node that never receives a message, a launch file that starts everything except the one node that mattered, a policy that looks fine on paper but never reaches the goal in sim. This skill frames the robotics-specific test pyramid and states the non-negotiable bar: a robium build is not done until its smoke test passes. It does not re-teach `launch_testing`/pytest mechanics for ROS 2 (that's `ros2`) or the `lerobot-eval` CLI (that's `lerobot`) — it frames both as test-pyramid layers and routes to them. ## When to use this skill - Setting up tests for any new robium project — this should be planned into the build from the start, not bolted on after the fact. - The trigger phrases in the description: 'test the robot app', 'how do I test this node', 'smoke test', 'regression test in sim'. - Before claiming any robotics app or sample works — a claim of "done" without a passing smoke test is not verified, it's a guess. - Load alongside whatever skill is building the thing under test — `ros2`/ `nav2`/`gazebo` for the navigation vertical, `lerobot` for the manipulation vertical — this skill supplies the test framing, not a replacement for either. - Cross-references — go to the sibling skill instead when the question is: - ROS 2 `launch_testing`/pytest mechanics themselves (fixtures, process actions, assertions) → the upstream launch_testing README