|
Package Summary
Tags | No category tags. |
Version | 1.1.17 |
License | Apache-2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-planning/navigation2.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2024-11-22 |
Dev Status | DEVELOPED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Carlos Orduno
Authors
System Tests
The package provides tests for Component-Testing, Subsystem-Testing, and Full-System integration. Its main goal is to provide a location for smoke and integration tests of the navigation system to ensure that things are working properly on a high level. Unit and specific subsystem testing happens in the packages specific to those algorithms.
Most tests in this package will spin up Gazebo instances of a robot in an environment to have the robot complete some task in the space while tracking a specific modules results. Some examples include
- System tests of a robot in a sandbox environment trying navigate to pose, navigate through poses, and waypoint following navigation types
- Random planning of thousands of paths in a generated environment to ensure default planners are working properly
- Testing the system can be brought up and down on the lifecycle transitions successfully multiple times
- Testing that the keepout and speed restricted zones work in a practical environment without going into keepout zones and slowing in speed restricted areas
- Testing behaviors in a sandbox environment to ensure they trigger and complete collision checking properly
- Testing system failures are properly recorded and can be recovered from
This is primarily for use in Nav2 CI to establish a high degree of maintainer confidence when merging in large architectural changes to the Nav2 project. However, this is also useful to test installs of Nav2 locally or for additional information.
Wiki Tutorials
Package Dependencies
System Dependencies
Name |
---|
lcov |
python3-zmq |
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged nav2_system_tests at Robotics Stack Exchange
|
Package Summary
Tags | No category tags. |
Version | 1.2.10 |
License | Apache-2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-planning/navigation2.git |
VCS Type | git |
VCS Version | iron |
Last Updated | 2024-10-02 |
Dev Status | DEVELOPED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Carlos Orduno
Authors
System Tests
The package provides tests for Component-Testing, Subsystem-Testing, and Full-System integration. Its main goal is to provide a location for smoke and integration tests of the navigation system to ensure that things are working properly on a high level. Unit and specific subsystem testing happens in the packages specific to those algorithms.
Most tests in this package will spin up Gazebo instances of a robot in an environment to have the robot complete some task in the space while tracking a specific modules results. Some examples include
- System tests of a robot in a sandbox environment trying navigate to pose, navigate through poses, and waypoint following navigation types
- Random planning of thousands of paths in a generated environment to ensure default planners are working properly
- Testing the system can be brought up and down on the lifecycle transitions successfully multiple times
- Testing that the keepout and speed restricted zones work in a practical environment without going into keepout zones and slowing in speed restricted areas
- Testing behaviors in a sandbox environment to ensure they trigger and complete collision checking properly
- Testing system failures are properly recorded and can be recovered from
This is primarily for use in Nav2 CI to establish a high degree of maintainer confidence when merging in large architectural changes to the Nav2 project. However, this is also useful to test installs of Nav2 locally or for additional information.
Wiki Tutorials
Package Dependencies
System Dependencies
Name |
---|
lcov |
python3-zmq |
Dependant Packages
Launch files
Messages
Services
Recent questions tagged nav2_system_tests at Robotics Stack Exchange
|
Package Summary
Tags | No category tags. |
Version | 1.3.3 |
License | Apache-2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-planning/navigation2.git |
VCS Type | git |
VCS Version | jazzy |
Last Updated | 2024-11-21 |
Dev Status | DEVELOPED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Carlos Orduno
Authors
System Tests
The package provides tests for Component-Testing, Subsystem-Testing, and Full-System integration. Its main goal is to provide a location for smoke and integration tests of the navigation system to ensure that things are working properly on a high level. Unit and specific subsystem testing happens in the packages specific to those algorithms.
Most tests in this package will spin up Gazebo instances of a robot in an environment to have the robot complete some task in the space while tracking a specific modules results. Some examples include
- System tests of a robot in a sandbox environment trying navigate to pose, navigate through poses, and waypoint following navigation types
- Random planning of thousands of paths in a generated environment to ensure default planners are working properly
- Testing the system can be brought up and down on the lifecycle transitions successfully multiple times
- Testing that the keepout and speed restricted zones work in a practical environment without going into keepout zones and slowing in speed restricted areas
- Testing behaviors in a sandbox environment to ensure they trigger and complete collision checking properly
- Testing system failures are properly recorded and can be recovered from
This is primarily for use in Nav2 CI to establish a high degree of maintainer confidence when merging in large architectural changes to the Nav2 project. However, this is also useful to test installs of Nav2 locally or for additional information.
Wiki Tutorials
Package Dependencies
System Dependencies
Name |
---|
lcov |
python3-zmq |
Dependant Packages
Launch files
Messages
Services
Recent questions tagged nav2_system_tests at Robotics Stack Exchange
|
Package Summary
Tags | No category tags. |
Version | 1.0.12 |
License | Apache-2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-planning/navigation2.git |
VCS Type | git |
VCS Version | galactic |
Last Updated | 2022-09-15 |
Dev Status | DEVELOPED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Carlos Orduno
Authors
System Tests
The package provides tests for components, subsystems and full system integration.
Unit tests are not included, these should be provided within each component or package.
1. Component Testing
Test a component’s ROS API (Pub/Sub/Service).
-
Controller
-
World Model
-
Costmaps
2. Subsystem Testing
Test the integration of several components and subsystems.
-
Support modules (Mapping, Perception, Prediction, Localization
-
Navigation core (Navigator, Planner, Controller)
-
Support modules and navigation core
-
Command chain (Mission Planning, Mission Execution, Navigation System, Robot Interface)
3. System Testing
Test the lifecycle startup and shutdown of nodes.
Test the integration of all subsystems.
Wiki Tutorials
Package Dependencies
System Dependencies
Name |
---|
lcov |
python3-zmq |