We have a couple of unit tests already, and #172 will add some more.
Right now these are built as part of the main executable, but that's not needed.
We could consider creating an additional VS project as part of the MotoROS2 solution which builds a stand-alone unit testing executable. That executable could be deployed on our test controller much easier and runs would be much faster as they would only exercise the code-under-test (instead of starting a full MotoROS2 instance).
We have a couple of unit tests already, and #172 will add some more.
Right now these are built as part of the main executable, but that's not needed.
We could consider creating an additional VS project as part of the MotoROS2 solution which builds a stand-alone unit testing executable. That executable could be deployed on our test controller much easier and runs would be much faster as they would only exercise the code-under-test (instead of starting a full MotoROS2 instance).