See also: ApexAI/apex_rostest#18
We plan to integrate the work done in https://github.com/ApexAI/apex_rostest into this repository and at the same time separate the ROS specific components of launch into a new separate repository (https://github.com/ros2/launch_ros).
This is the planned layout:
- repository ros2/launch:
- package
launch
- package
launch_testing
- will be combined with the package
apex_launchtest from the repository ApexAI/apex_rostest
- will also contain a CLI for running tests, name is TBD
- package
launch_testing_ament_cmake (new)
- will be based on the package
apex_launchtest_cmake from the repository ApexAI/apex_rostest
- will provide cmake integration like add_launch_test(...) (name TDB) which implicitly calls the test runner rather than pytest
- in the future may optionally invoke pytest instead (still working on integration)
- will depend on the package
launch_testing
- repository ros2/launch_ros (new)
- package
launch_ros
- package
test_launch_ros
- package
ros2launch
- package
launch_ros_testing (new)
- will be based on the package
apex_launchtest_ros from the repository ApexAI/apex_rostest
- also, may be based on the launch_testing package in ros2/launch repository as well (depends on what we find)
- repository ros2/rostest (new)
- package
rostest (new)
- will contain a placeholder CLI called
rostest (or ros2 test?) which will alias to the CLI in launch_testing
- will allow for future ROS specific options for manual test running
- may contain cmake macros like
add_rostest(...) to allow for future ROS specific integration
- will serve as the "single point of entry" for ROS 2 users, i.e. they will
<test_depend>rostest</test_depend>
- will contain high level documentation and examples
Action items:
Connected to #161.
See also: ApexAI/apex_rostest#18
We plan to integrate the work done in https://github.com/ApexAI/apex_rostest into this repository and at the same time separate the ROS specific components of launch into a new separate repository (https://github.com/ros2/launch_ros).
This is the planned layout:
launchlaunch_testingapex_launchtestfrom the repository ApexAI/apex_rostestlaunch_testing_ament_cmake(new)apex_launchtest_cmakefrom the repository ApexAI/apex_rostestlaunch_testinglaunch_rostest_launch_rosros2launchlaunch_ros_testing(new)apex_launchtest_rosfrom the repository ApexAI/apex_rostestrostest(new)rostest(orros2 test?) which will alias to the CLI inlaunch_testingadd_rostest(...)to allow for future ROS specific integration<test_depend>rostest</test_depend>Action items:
apex_rostestapex_rostest/AMENT_IGNOREto prevent them from getting picked up by CIapex_rostest/apex_launchtestintolaunch_testinglaunch_testing_ament_cmakeand merges code fromapex_rostest/apex_launchtest_cmakelaunch_ros_testingand merges code fromapex_rostest/apex_launchtest_rosapex_rostestbased coderostestpackage and add to it: (Add ros_testing metapackage and ros2test CLI package ros_testing#1)launch_testing)Connected to #161.