replay_testing
- Software
- Middleware
- Tool
A ROS2 framework for authoring and running replay tests: it replays recorded MCAP data into your own nodes and checks the output with unittest-based analysis.
Made by Polymath Robotics.
Source on GitHub: github.com/polymathrobotics/replay_testing (opens in a new tab). Facts read at commit ed19bf0 (opens in a new tab).
Licenses
- Code
- Apache-2.0 (opens in a new tab)
Read by Robotheca from LICENSE (opens in a new tab) (Apache-2.0) at commit ed19bf0 (opens in a new tab), on 22 Oct 2026.
- Commercial use
- Yes
What it does
- Replays previously recorded MCAP data into your ROS2 nodes so you can iterate locally instead of on the robot.
- Defines test phases via Python decorators: fixtures, run, and analyze, all required for a replay test.
- Supports parameter sweeps, QoS overrides, and clock configuration including optional /clock publishing.
- Analyze step wraps unittest.TestCase and gives access to an MCAP reader for asserting on output messages.
- Provides a CMake macro for running replay tests in colcon test and CI, producing xunit XML results.
- Can store large MCAP files in S3-compatible storage through an S3Fixture helper.
Written by Robotheca from the project's README (opens in a new tab) at commit ed19bf0.
Getting started
- Difficulty
- Advanced
- How to start
- The project's README (opens in a new tab)
Maintenance
- Status
- Maintained: a commit in the last 12 months
- Newest commit
- 28 Apr 2026 on main
- Latest release
- None published on GitHub
Checked on GitHub on 22 Oct 2026.
Links
Robots that can run it
No robot on Robotheca is linked to it yet. Links come from a robot's robot.yaml, from its dependency files read as text, or from Robotheca's editors.
Robotheca lists software as a reference: nothing is hosted or run here, and every fact links to where it was read.