Test/add cli tests

[ielson]

Closes #357

Summary

Add tests for ros2 control CLI verbs under 'controller_manager/test', using the existing local controller_manager test setup instead of depending on ros2_control_demos.

The new tests cover CLI behavior for:

• list_controllers
• list_controller_types
• list_hardware_components
• list_hardware_interfaces
• load_controller
• reload_controller_libraries --force-kill
• reload_controller_libraries failure path without --force-kill
• set_controller_state
• switch_controllers --best-effort
• cleanup_controller
• unload_controller
• view_hardware_status

Files added:

• test_ros2_controlcli_verbs.py
• test_ros2_controlcli.yaml

Testing

• colcon test --packages-select controller_manager --ctest-args -R test_ros2_controlcli_verbs --output-on-failure
• colcon test-result --all --verbose

---

Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:

1. Limited scope. Your PR should do one thing or one set of things. Avoid adding “random fixes” to PRs. Put those on separate PRs.
2. Give your PR a descriptive title. Add a short summary, if required.
3. Make sure the pipeline is green.
4. Don’t be afraid to request reviews from maintainers.
5. New code = new tests. If you are adding new functionality, always make sure to add some tests exercising the code and serving as live documentation of your original intention.

To send us a pull request, please:

• Fork the repository.
• Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
• Ensure local tests pass. (colcon test and pre-commit run (requires you to install pre-commit by pip3 install pre-commit)
• Commit to your fork using clear commit messages.
• Send a pull request, answering any default questions in the pull request interface.
• Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.

[ielson]

PR is ready for review, from the requested checks just couldn't check if the other workflows passes, because they are awaiting approval

[bmagyar]

CI kicked off!

[ielson]

hey @bmagyar I believe that the tests didn't pass before because my branch was outdated but I have merged the new changes on it.
Can you approve the CI again?

[ielson]

@bmagyar friendly ping, can you kick the CI off again?

[christophfroehlich]

Please have a look at the failing tests. All new tests are failing?
Pre-commit ones are obvious, all lyrical-testing and main-testing jobs succeed on the current master, the main ones are known to be failing currently.

2026-05-14T13:04:31.2891181Z     test_ros2_controlcli_verbs.TestRos2ControlCliVerbs.test_cleanup_controller failed
2026-05-14T13:04:31.2892232Z     test_ros2_controlcli_verbs.TestRos2ControlCliVerbs.test_list_controller_types failed
2026-05-14T13:04:31.2893156Z     test_ros2_controlcli_verbs.TestRos2ControlCliVerbs.test_list_controllers failed
2026-05-14T13:04:31.2894052Z     test_ros2_controlcli_verbs.TestRos2ControlCliVerbs.test_list_hardware_components failed
2026-05-14T13:04:31.2895005Z     test_ros2_controlcli_verbs.TestRos2ControlCliVerbs.test_list_hardware_interfaces failed
2026-05-14T13:04:31.2896157Z     test_ros2_controlcli_verbs.TestRos2ControlCliVerbs.test_load_controller failed
2026-05-14T13:04:31.2897243Z     test_ros2_controlcli_verbs.TestRos2ControlCliVerbs.test_reload_controller_libraries_force_kill failed
2026-05-14T13:04:31.2898313Z     test_ros2_controlcli_verbs.TestRos2ControlCliVerbs.test_set_controller_state failed
2026-05-14T13:04:31.2899250Z     test_ros2_controlcli_verbs.TestRos2ControlCliVerbs.test_switch_controllers_best_effort failed
2026-05-14T13:04:31.2900416Z     test_ros2_controlcli_verbs.TestRos2ControlCliVerbs.test_unload_controller failed
2026-05-14T13:04:31.2901321Z     test_ros2_controlcli_verbs.TestRos2ControlCliVerbs.test_view_hardware_status failed