Repository Summary
Checkout URI | https://github.com/ros2/system_tests.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2023-11-21 |
Dev Status | DEVELOPED |
CI status | No Continuous Integration |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Packages
Name | Version |
---|---|
test_cli | 0.12.4 |
test_cli_remapping | 0.12.4 |
test_communication | 0.12.4 |
test_quality_of_service | 0.12.4 |
test_rclcpp | 0.12.4 |
test_security | 0.12.4 |
README
System Tests
New system tests may be added when new functionality needs to be tested using the complete ROS 2 core. Before contributing new system tests please discuss the tests you would like to add with the ROS 2 team. If you’re implementing new features that may benefit from additional system tests you can ask the reviewers of your pull requests whether system tests are desired. If you would like to add system tests for existing features please open an issue explaining the proposed tests and rationale so it can be reviewed before you start work.
When implementing additional system tests on you could start by using existing tests as a template.
In the test_rclcpp
package there is a test of a node with a single service.
This test includes a server executable and a client executable.
The server executable is a “plain” ROS 2 node implementing a service and the client executable contains GTEST macros testing functionality.
These are included in the build from this stanza of CMakeLists.txt
and added to this macro of tests to be run for each rmw implementation.
CONTRIBUTING
Any contribution that you make to this repository will be under the Apache 2 License, as dictated by that license:
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
Contributors must sign-off each commit by adding a Signed-off-by: ...
line to commit messages to certify that they have the right to submit
the code they are contributing to the project according to the
Developer Certificate of Origin (DCO).
Repository Summary
Checkout URI | https://github.com/ros2/system_tests.git |
VCS Type | git |
VCS Version | iron |
Last Updated | 2024-02-07 |
Dev Status | DEVELOPED |
CI status | No Continuous Integration |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Packages
Name | Version |
---|---|
test_cli | 0.15.3 |
test_cli_remapping | 0.15.3 |
test_communication | 0.15.3 |
test_quality_of_service | 0.15.3 |
test_rclcpp | 0.15.3 |
test_security | 0.15.3 |
README
System Tests
New system tests may be added when new functionality needs to be tested using the complete ROS 2 core. Before contributing new system tests please discuss the tests you would like to add with the ROS 2 team. If you’re implementing new features that may benefit from additional system tests you can ask the reviewers of your pull requests whether system tests are desired. If you would like to add system tests for existing features please open an issue explaining the proposed tests and rationale so it can be reviewed before you start work.
When implementing additional system tests on you could start by using existing tests as a template.
In the test_rclcpp
package there is a test of a node with a single service.
This test includes a server executable and a client executable.
The server executable is a “plain” ROS 2 node implementing a service and the client executable contains GTEST macros testing functionality.
These are included in the build from this stanza of CMakeLists.txt
and added to this macro of tests to be run for each rmw implementation.
CONTRIBUTING
Any contribution that you make to this repository will be under the Apache 2 License, as dictated by that license:
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
Contributors must sign-off each commit by adding a Signed-off-by: ...
line to commit messages to certify that they have the right to submit
the code they are contributing to the project according to the
Developer Certificate of Origin (DCO).
Repository Summary
Checkout URI | https://github.com/ros2/system_tests.git |
VCS Type | git |
VCS Version | jazzy |
Last Updated | 2024-11-28 |
Dev Status | DEVELOPED |
CI status | No Continuous Integration |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Packages
Name | Version |
---|---|
test_cli | 0.20.2 |
test_cli_remapping | 0.20.2 |
test_communication | 0.20.2 |
test_quality_of_service | 0.20.2 |
test_rclcpp | 0.20.2 |
test_security | 0.20.2 |
README
System Tests
New system tests may be added when new functionality needs to be tested using the complete ROS 2 core. Before contributing new system tests please discuss the tests you would like to add with the ROS 2 team. If you’re implementing new features that may benefit from additional system tests you can ask the reviewers of your pull requests whether system tests are desired. If you would like to add system tests for existing features please open an issue explaining the proposed tests and rationale so it can be reviewed before you start work.
When implementing additional system tests on you could start by using existing tests as a template.
In the test_rclcpp
package there is a test of a node with a single service.
This test includes a server executable and a client executable.
The server executable is a “plain” ROS 2 node implementing a service and the client executable contains GTEST macros testing functionality.
These are included in the build from this stanza of CMakeLists.txt
and added to this macro of tests to be run for each rmw implementation.
CONTRIBUTING
Any contribution that you make to this repository will be under the Apache 2 License, as dictated by that license:
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
Contributors must sign-off each commit by adding a Signed-off-by: ...
line to commit messages to certify that they have the right to submit
the code they are contributing to the project according to the
Developer Certificate of Origin (DCO).
Repository Summary
Checkout URI | https://github.com/ros2/system_tests.git |
VCS Type | git |
VCS Version | rolling |
Last Updated | 2024-11-28 |
Dev Status | DEVELOPED |
CI status | No Continuous Integration |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Packages
Name | Version |
---|---|
test_cli | 0.22.1 |
test_cli_remapping | 0.22.1 |
test_communication | 0.22.1 |
test_quality_of_service | 0.22.1 |
test_rclcpp | 0.22.1 |
test_security | 0.22.1 |
README
System Tests
New system tests may be added when new functionality needs to be tested using the complete ROS 2 core. Before contributing new system tests please discuss the tests you would like to add with the ROS 2 team. If you’re implementing new features that may benefit from additional system tests you can ask the reviewers of your pull requests whether system tests are desired. If you would like to add system tests for existing features please open an issue explaining the proposed tests and rationale so it can be reviewed before you start work.
When implementing additional system tests on you could start by using existing tests as a template.
In the test_rclcpp
package there is a test of a node with a single service.
This test includes a server executable and a client executable.
The server executable is a “plain” ROS 2 node implementing a service and the client executable contains GTEST macros testing functionality.
These are included in the build from this stanza of CMakeLists.txt
and added to this macro of tests to be run for each rmw implementation.
CONTRIBUTING
Any contribution that you make to this repository will be under the Apache 2 License, as dictated by that license:
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
Contributors must sign-off each commit by adding a Signed-off-by: ...
line to commit messages to certify that they have the right to submit
the code they are contributing to the project according to the
Developer Certificate of Origin (DCO).
Repository Summary
Checkout URI | https://github.com/ros2/system_tests.git |
VCS Type | git |
VCS Version | galactic |
Last Updated | 2022-12-07 |
Dev Status | DEVELOPED |
CI status | No Continuous Integration |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Packages
Name | Version |
---|---|
test_cli | 0.11.2 |
test_cli_remapping | 0.11.2 |
test_communication | 0.11.2 |
test_quality_of_service | 0.11.2 |
test_rclcpp | 0.11.2 |
test_security | 0.11.2 |
README
System Tests
New system tests may be added when new functionality needs to be tested using the complete ROS 2 core. Before contributing new system tests please discuss the tests you would like to add with the ROS 2 team. If you’re implementing new features that may benefit from additional system tests you can ask the reviewers of your pull requests whether system tests are desired. If you would like to add system tests for existing features please open an issue explaining the proposed tests and rationale so it can be reviewed before you start work.
When implementing additional system tests on you could start by using existing tests as a template.
In the test_rclcpp
package there is a test of a node with a single service.
This test includes a server executable and a client executable.
The server executable is a “plain” ROS 2 node implementing a service and the client executable contains GTEST macros testing functionality.
These are included in the build from this stanza of CMakeLists.txt
and added to this macro of tests to be run for each rmw implementation.
CONTRIBUTING
Any contribution that you make to this repository will be under the Apache 2 License, as dictated by that license:
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
Contributors must sign-off each commit by adding a Signed-off-by: ...
line to commit messages to certify that they have the right to submit
the code they are contributing to the project according to the
Developer Certificate of Origin (DCO).
Repository Summary
Checkout URI | https://github.com/ros2/system_tests.git |
VCS Type | git |
VCS Version | foxy |
Last Updated | 2022-01-31 |
Dev Status | DEVELOPED |
CI status | No Continuous Integration |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Packages
Name | Version |
---|---|
test_cli | 0.9.2 |
test_cli_remapping | 0.9.2 |
test_communication | 0.9.2 |
test_quality_of_service | 0.9.2 |
test_rclcpp | 0.9.2 |
test_security | 0.9.2 |
README
System Tests
New system tests may be added when new functionality needs to be tested using the complete ROS 2 core. Before contributing new system tests please discuss the tests you would like to add with the ROS 2 team. If you’re implementing new features that may benefit from additional system tests you can ask the reviewers of your pull requests whether system tests are desired. If you would like to add system tests for existing features please open an issue explaining the proposed tests and rationale so it can be reviewed before you start work.
When implementing additional system tests on you could start by using existing tests as a template.
In the test_rclcpp
package there is a test of a node with a single service.
This test includes a server executable and a client executable.
The server executable is a “plain” ROS 2 node implementing a service and the client executable contains GTEST macros testing functionality.
These are included in the build from this stanza of CMakeLists.txt
and added to this macro of tests to be run for each rmw implementation.
CONTRIBUTING
Any contribution that you make to this repository will be under the Apache 2 License, as dictated by that license:
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
Contributors must sign-off each commit by adding a Signed-off-by: ...
line to commit messages to certify that they have the right to submit
the code they are contributing to the project according to the
Developer Certificate of Origin (DCO).