This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
Software Style: Testing
Alan Chung Ma edited this page Apr 30, 2022
·
1 revision
TODO(Issue #1): Please refactor this section HEAVILY. Feel free to use from what is already here but this needs a complete overhaul.
RViz https://www.stereolabs.com/docs/ros/rviz/ Gazebo + ROS
TODO
In addition to simulation testing, writing unit tests is important for a few reasons:
- Validates the code is doing what you want it to
- Forces you to break up the code into logical parts (i.e. Single responsibility principle)
- Serves as a great form of documentation for the code you have tests for.
- Ensures that changes in the future don’t break the code in case it looks like it works in simulation
ROS Unit Testing Guides
- C++: http://wiki.ros.org/CppStyleGuide#Testing
- Python: None yet :(
In addition, we recommend reading the chapters “Testing Overview” and “Unit Testing” from the book “Software engineering at Google”. The book is available as an e-copy through the Purdue library.