Testing

The repository ships three standalone Zephyr test programs that share the same build system as the main application. Each one replaces the controller with a small driver that exercises one subsystem in isolation.

Pass at most one of the flags below; if more than one is passed, only the last takes effect.

Unit test (node + DDS round-trip)

$ ./build.sh --unit-test

Builds actuation_module/test/unit_test.cpp. The test creates a DDS publisher and subscriber on the same topic, drives a node timer, and checks that messages arrive and callbacks fire as expected. Useful as a smoke test after changes to include/common/node/ or include/common/dds/.

DDS publisher only

$ ./build.sh --dds-publisher

Builds actuation_module/test/dds_pub.cpp. The firmware creates a DDS writer and publishes sample messages in a loop. Pair with a DDS subscriber on another machine (for example ddsperf) to validate discovery and network path.

DDS subscriber only

$ ./build.sh --dds-subscriber

Builds actuation_module/test/dds_sub.cpp. The firmware creates a DDS reader and logs every message it receives. Pair with an external publisher to validate the inbound path.

Running tests

All test binaries are produced at build/actuation_module/zephyr/zephyr.elf and are deployed in exactly the same way as the main application:

Clean between builds if switching flags:

$ ./build.sh -c