robotics-testing

Solid

Testing strategies, patterns, and tools for robotics software. Use this skill when writing unit tests, integration tests, simulation tests, or hardware-in-the-loop tests for robot systems. Trigger whenever the user mentions testing ROS nodes, pytest with ROS, launch_testing, simulation testing, CI/CD for robotics, test fixtures for sensors, mock hardware, deterministic replay, regression testing for robot behaviors, or validating perception/planning/control pipelines. Also covers property-based testing for kinematics, fuzz testing for message handlers, and golden-file testing for trajectories.

Testing & QA 324 stars 45 forks Updated 5 days ago Apache-2.0

Install

View on GitHub

Quality Score: 90/100

Stars 20%
84
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Robotics Testing Skill ## When to Use This Skill - Writing unit tests for ROS1/ROS2 nodes - Setting up integration tests with launch_testing - Mocking hardware (sensors, actuators) for CI/CD - Building simulation-based test suites - Testing perception pipelines with ground truth - Validating trajectory planners and controllers - Setting up CI/CD pipelines for robotics packages - Debugging flaky tests in robotics systems ## The Robotics Testing Pyramid ``` ╱╲ ╱ ╲ Field Tests ╱ ╲ (Real robot, real environment) ╱──────╲ ╱ ╲ Hardware-in-the-Loop (HIL) ╱ ╲ (Real hardware, controlled environment) ╱────────────╲ ╱ ╲ Simulation Tests ╱ ╲ (Full sim, realistic physics) ╱──────────────────╲ ╱ ╲ Integration Tests ╱ ╲ (Multi-node, message passing) ╱────────────────────────╲ ╱ ╲ Unit Tests ╱____________________________╲ (Single function/class, fast, deterministic) MORE tests at the bottom, FEWER at the top. Bottom = fast, cheap, deterministic. Top = slow, expensive, realistic. ``` ## Unit Testing Patterns ### Testing ROS2 Nodes with pytest ```python # test_perception_node.py import pytest import rclpy from rclpy.node import Node from sensor_msgs.msg impor...

Details

Author
arpitg1304
Repository
arpitg1304/robotics-agent-skills
Created
5 months ago
Last Updated
5 days ago
Language
Python
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Testing & QA Listed

testing

Test-driven robotics development: smoke tests for launch files, sim-based regression tests, node-level unit tests, policy eval as a test, and CI patterns for robotics repos. Use when: 'test the robot app', 'how do I test this node', 'smoke test', 'regression test in sim', setting up tests for a new robotics project, or before claiming any robotics app works. Applies to both verticals: launch_testing and pytest for ROS 2 apps; deterministic small-scale eval runs for ML policies. Load alongside whatever skill is building the thing under test. Not for: general (non-robotics) testing practices.

0 Updated today
robium-ai
AI & Automation Solid

ros2-development

Comprehensive best practices, design patterns, and common pitfalls for ROS2 (Robot Operating System 2) development. Use this skill when building ROS2 nodes, packages, launch files, components, or debugging ROS2 systems. Trigger whenever the user mentions ROS2, colcon, rclpy, rclcpp, DDS, QoS, lifecycle nodes, managed nodes, ROS2 launch, ROS2 parameters, ROS2 actions, nav2, MoveIt2, micro-ROS, or any ROS2-era robotics middleware. Also trigger for ROS2 workspace setup, DDS tuning, intra-process communication, ROS2 security, or deploying ROS2 in production. Also trigger for colcon build issues, ament_cmake, ament_python, CMakeLists.txt for ROS2, package.xml dependencies, rosdep, workspace overlays, custom message generation, or ROS2 build troubleshooting. Covers Humble, Iron, Jazzy, and Rolling distributions.

324 Updated 5 days ago
arpitg1304
AI & Automation Solid

ros1-development

Best practices, design patterns, and common pitfalls for ROS1 (Robot Operating System 1) development. Use this skill when building ROS1 nodes, packages, launch files, or debugging ROS1 systems. Trigger whenever the user mentions ROS1, catkin, rospy, roscpp, roslaunch, roscore, rostopic, tf, actionlib, message types, services, or any ROS1-era robotics middleware. Also trigger for migrating ROS1 code to ROS2, maintaining legacy ROS1 systems, or building ROS1-ROS2 bridges. Covers catkin workspaces, nodelets, dynamic reconfigure, pluginlib, and the full ROS1 ecosystem.

324 Updated 5 days ago
arpitg1304