Package Summary

Version 0.7.2
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/selfpatch/ros2_medkit.git
VCS Type git
VCS Version main
Last Updated 2026-11-22
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Integration tests and demo nodes for ros2_medkit

Maintainers

  • bburda

Authors

No additional authors.

ros2_medkit_integration_tests

Integration tests, demo nodes, and shared test utilities for ros2_medkit.

Overview

This package contains everything needed to validate the ros2_medkit system end-to-end:

  • Demo nodes – automotive-themed C++ nodes (sensors, actuators, services, actions) that produce realistic ROS 2 traffic for testing
  • Feature tests – focused tests that validate individual API features (data access, operations, faults, SSE, CORS, auth, etc.)
  • Scenario tests – end-to-end stories that exercise multi-step workflows (fault lifecycle, action execution, discovery modes, subscriptions, etc.)
  • Shared test library (ros2_medkit_test_utils) – base test case, launch helpers, and assertion utilities shared across all test files

Package Structure

ros2_medkit_integration_tests/
  demo_nodes/           # C++ demo node sources
  launch/               # demo_nodes.launch.py
  ros2_medkit_test_utils/
    __init__.py
    constants.py        # DEFAULT_PORT, timeouts
    coverage.py         # GCOV_PREFIX helpers for CI
    gateway_test_case.py  # GatewayTestCase base class
    launch_helpers.py   # create_test_launch(), DEMO_NODE_REGISTRY
  test/
    features/           # Focused API feature tests
    scenarios/          # End-to-end workflow tests

Running Tests

# Build everything
colcon build --symlink-install
source install/setup.bash

# All integration tests
colcon test --packages-select ros2_medkit_integration_tests
colcon test-result --verbose

# Single test
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -R test_data_read

# Feature tests only
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -L feature

# Scenario tests only
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -L scenario

Demo Nodes

Launch all demo nodes for manual testing or the web UI:

ros2 launch ros2_medkit_integration_tests demo_nodes.launch.py

Node Namespace Type Description
temp_sensor /powertrain/engine Publisher Engine temperature (2 Hz)
rpm_sensor /powertrain/engine Publisher RPM readings (2 Hz)
pressure_sensor /chassis/brakes Publisher Brake pressure (2 Hz)
status_sensor /body/door/front_left Publisher Door open/closed (0.5 Hz)
lidar_sensor /perception/lidar Publisher + Fault reporter LaserScan with fault detection
actuator /chassis/brakes Subscriber + Publisher Brake actuator (command/feedback)
controller /body/lights Subscriber + Publisher Light controller (command/status)
calibration /powertrain/engine Service Trigger-based calibration
long_calibration /powertrain/engine Action Fibonacci-based long-running action
dual_calibration /testrig/dual Services + Actions left/calibrate and right/calibrate, left/sweep and right/sweep - one provider carrying each operation short name twice, so the ROS path is the only id that separates the copies

Crash reports

Every demo binary installs a fatal-signal handler before anything else runs. Most get it from run_demo_node() in include/ros2_medkit_integration_tests/demo_node_main.hpp; the two that cannot use that helper - unresponsive_param_node and managed_lifecycle_node, which own their shutdown sequence - call install_crash_backtrace() themselves. A node killed by SIGSEGV, SIGBUS or SIGABRT writes its stack to stderr, so launch_testing captures it with the rest of the process output:

MEDKIT-CRASH signal=SIGSEGV
/path/to/demo_brake_pressure_sensor(+0x129cb) [0x5603199349cb]
/opt/ros/<distro>/lib/libfastdds.so.3(...) [0x...]
MEDKIT-CRASH end

Grep a CI log for MEDKIT-CRASH to find one. Frames from our own binaries come back as binary(+0xOFFSET) because the release build has no exported symbols; resolve them with addr2line -e <binary> <offset>. The process still dies from

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package ros2_medkit_integration_tests

0.7.2 (2026-11-19)

  • The package builds as a binary package again. topics_test_plugin and its lookup of ros2_medkit_gateway are inside BUILD_TESTING, because the gateway is a test_depend. 0.7.1 failed to build on the buildfarm for Jazzy and Lyrical (#805). The binary package no longer installs topics_test_plugin (#806)
  • Contributors: \@mfaferek93

0.7.1 (2026-11-18)

  • Test only: coverage for recording manifests and per-file downloads, the gateway's helper nodes, fault lists on a chain of gateways, trigger and subscription paths, and steadier timing in the launch tests
  • Contributors: \@bburda, \@mfaferek93

0.7.0 (2026-08-27)

  • Every integration launch test runs on its own DDS domain, taken when the test starts and held through an open socket for exactly as long as it runs, so a crash or a SIGKILL releases it the same way an ordinary exit does. This replaces the hand-maintained per-package domain pools, which had to stay pairwise disjoint because colcon runs one ctest per package in parallel and a CTest RESOURCE_LOCK binds only inside a single ctest run (#551, #597)
  • Feature tests are registered by glob: a file dropped into test/features/*.test.py is registered with its port and domain assigned automatically, so no explicit registration is needed and none can bypass GATEWAY_TEST_PORT
  • Inline gateways and fault managers go through the shared launch helpers rather than each test hand-building its own, which also fixed the SIGKILL these tests hit under coverage instrumentation (#554)
  • The Python in this package is linted (#598), and the package is instrumented for coverage (#582)
  • Flaky suites are fixed at their cause rather than retried: the OPC UA Alarms and Conditions test, the action-status and diagnostic-bridge fault paths, the operation-handlers fixture, type_info caching and the documentation linkcheck (#504, #636)
  • Contributors: \@bburda, \@mfaferek93, \@YueBit

0.6.0 (2026-06-22)

  • New suites covering the SOVD entity status endpoints (REQ_INTEROP_076), lifecycle-aware app and component status (#455), and fault-storm capture liveness under bounded concurrency (#456)
  • Contributors: \@bburda

0.5.0 (2026-06-08)

  • New peer-aggregation suites: peer aggregation, cross-ECU fan-out across all resource types, daisy-chain hierarchical aggregation, leaf-collision aggregation, and cross-ECU log aggregation
  • New SOVD-aligned entity-model suites: runtime entity model, flat entity tree without areas, hybrid suppression, and per-entity fault scope isolation
  • New OpenAPI conformance suites: test_openapi_callability and test_openapi_response_drift validate the published spec against live responses
  • New graph-event discovery suite covering rclcpp graph-event driven discovery refresh
  • Coverage for the GET /apps/{id}/belongs-to discovery endpoint, nested x-medkit vendor payloads (#385), version-info aggregation, and pending-after-register update status (#378)
  • Tests: centralized ROS_DOMAIN_ID allocation and widened shutdown timeouts for sanitizer overhead
  • Contributors: \@bburda, \@eclipse0922

0.4.0 (2026-03-20)

  • Integration tests for SOVD resource locking (acquire, release, extend, fault clear with locks, expiration, parent propagation)
  • Integration tests for SOVD script execution endpoints (all formats, params, output, failure, lifecycle)
  • Integration tests for graph provider plugin (external plugin loading, entity introspection)
  • Integration tests for beacon discovery plugins (topic beacon, parameter beacon)
  • Integration tests for OpenAPI/docs endpoint
  • Integration tests for logging endpoints (/logs, /logs/configuration)
  • Integration tests for linux introspection plugins (launch_testing and Docker-based)
  • Port isolation per integration test via CMake-assigned unique ports
  • ROS_DOMAIN_ID isolation for integration tests

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged ros2_medkit_integration_tests at Robotics Stack Exchange

Package Summary

Version 0.7.2
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/selfpatch/ros2_medkit.git
VCS Type git
VCS Version main
Last Updated 2026-11-22
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Integration tests and demo nodes for ros2_medkit

Maintainers

  • bburda

Authors

No additional authors.

ros2_medkit_integration_tests

Integration tests, demo nodes, and shared test utilities for ros2_medkit.

Overview

This package contains everything needed to validate the ros2_medkit system end-to-end:

  • Demo nodes – automotive-themed C++ nodes (sensors, actuators, services, actions) that produce realistic ROS 2 traffic for testing
  • Feature tests – focused tests that validate individual API features (data access, operations, faults, SSE, CORS, auth, etc.)
  • Scenario tests – end-to-end stories that exercise multi-step workflows (fault lifecycle, action execution, discovery modes, subscriptions, etc.)
  • Shared test library (ros2_medkit_test_utils) – base test case, launch helpers, and assertion utilities shared across all test files

Package Structure

ros2_medkit_integration_tests/
  demo_nodes/           # C++ demo node sources
  launch/               # demo_nodes.launch.py
  ros2_medkit_test_utils/
    __init__.py
    constants.py        # DEFAULT_PORT, timeouts
    coverage.py         # GCOV_PREFIX helpers for CI
    gateway_test_case.py  # GatewayTestCase base class
    launch_helpers.py   # create_test_launch(), DEMO_NODE_REGISTRY
  test/
    features/           # Focused API feature tests
    scenarios/          # End-to-end workflow tests

Running Tests

# Build everything
colcon build --symlink-install
source install/setup.bash

# All integration tests
colcon test --packages-select ros2_medkit_integration_tests
colcon test-result --verbose

# Single test
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -R test_data_read

# Feature tests only
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -L feature

# Scenario tests only
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -L scenario

Demo Nodes

Launch all demo nodes for manual testing or the web UI:

ros2 launch ros2_medkit_integration_tests demo_nodes.launch.py

Node Namespace Type Description
temp_sensor /powertrain/engine Publisher Engine temperature (2 Hz)
rpm_sensor /powertrain/engine Publisher RPM readings (2 Hz)
pressure_sensor /chassis/brakes Publisher Brake pressure (2 Hz)
status_sensor /body/door/front_left Publisher Door open/closed (0.5 Hz)
lidar_sensor /perception/lidar Publisher + Fault reporter LaserScan with fault detection
actuator /chassis/brakes Subscriber + Publisher Brake actuator (command/feedback)
controller /body/lights Subscriber + Publisher Light controller (command/status)
calibration /powertrain/engine Service Trigger-based calibration
long_calibration /powertrain/engine Action Fibonacci-based long-running action
dual_calibration /testrig/dual Services + Actions left/calibrate and right/calibrate, left/sweep and right/sweep - one provider carrying each operation short name twice, so the ROS path is the only id that separates the copies

Crash reports

Every demo binary installs a fatal-signal handler before anything else runs. Most get it from run_demo_node() in include/ros2_medkit_integration_tests/demo_node_main.hpp; the two that cannot use that helper - unresponsive_param_node and managed_lifecycle_node, which own their shutdown sequence - call install_crash_backtrace() themselves. A node killed by SIGSEGV, SIGBUS or SIGABRT writes its stack to stderr, so launch_testing captures it with the rest of the process output:

MEDKIT-CRASH signal=SIGSEGV
/path/to/demo_brake_pressure_sensor(+0x129cb) [0x5603199349cb]
/opt/ros/<distro>/lib/libfastdds.so.3(...) [0x...]
MEDKIT-CRASH end

Grep a CI log for MEDKIT-CRASH to find one. Frames from our own binaries come back as binary(+0xOFFSET) because the release build has no exported symbols; resolve them with addr2line -e <binary> <offset>. The process still dies from

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package ros2_medkit_integration_tests

0.7.2 (2026-11-19)

  • The package builds as a binary package again. topics_test_plugin and its lookup of ros2_medkit_gateway are inside BUILD_TESTING, because the gateway is a test_depend. 0.7.1 failed to build on the buildfarm for Jazzy and Lyrical (#805). The binary package no longer installs topics_test_plugin (#806)
  • Contributors: \@mfaferek93

0.7.1 (2026-11-18)

  • Test only: coverage for recording manifests and per-file downloads, the gateway's helper nodes, fault lists on a chain of gateways, trigger and subscription paths, and steadier timing in the launch tests
  • Contributors: \@bburda, \@mfaferek93

0.7.0 (2026-08-27)

  • Every integration launch test runs on its own DDS domain, taken when the test starts and held through an open socket for exactly as long as it runs, so a crash or a SIGKILL releases it the same way an ordinary exit does. This replaces the hand-maintained per-package domain pools, which had to stay pairwise disjoint because colcon runs one ctest per package in parallel and a CTest RESOURCE_LOCK binds only inside a single ctest run (#551, #597)
  • Feature tests are registered by glob: a file dropped into test/features/*.test.py is registered with its port and domain assigned automatically, so no explicit registration is needed and none can bypass GATEWAY_TEST_PORT
  • Inline gateways and fault managers go through the shared launch helpers rather than each test hand-building its own, which also fixed the SIGKILL these tests hit under coverage instrumentation (#554)
  • The Python in this package is linted (#598), and the package is instrumented for coverage (#582)
  • Flaky suites are fixed at their cause rather than retried: the OPC UA Alarms and Conditions test, the action-status and diagnostic-bridge fault paths, the operation-handlers fixture, type_info caching and the documentation linkcheck (#504, #636)
  • Contributors: \@bburda, \@mfaferek93, \@YueBit

0.6.0 (2026-06-22)

  • New suites covering the SOVD entity status endpoints (REQ_INTEROP_076), lifecycle-aware app and component status (#455), and fault-storm capture liveness under bounded concurrency (#456)
  • Contributors: \@bburda

0.5.0 (2026-06-08)

  • New peer-aggregation suites: peer aggregation, cross-ECU fan-out across all resource types, daisy-chain hierarchical aggregation, leaf-collision aggregation, and cross-ECU log aggregation
  • New SOVD-aligned entity-model suites: runtime entity model, flat entity tree without areas, hybrid suppression, and per-entity fault scope isolation
  • New OpenAPI conformance suites: test_openapi_callability and test_openapi_response_drift validate the published spec against live responses
  • New graph-event discovery suite covering rclcpp graph-event driven discovery refresh
  • Coverage for the GET /apps/{id}/belongs-to discovery endpoint, nested x-medkit vendor payloads (#385), version-info aggregation, and pending-after-register update status (#378)
  • Tests: centralized ROS_DOMAIN_ID allocation and widened shutdown timeouts for sanitizer overhead
  • Contributors: \@bburda, \@eclipse0922

0.4.0 (2026-03-20)

  • Integration tests for SOVD resource locking (acquire, release, extend, fault clear with locks, expiration, parent propagation)
  • Integration tests for SOVD script execution endpoints (all formats, params, output, failure, lifecycle)
  • Integration tests for graph provider plugin (external plugin loading, entity introspection)
  • Integration tests for beacon discovery plugins (topic beacon, parameter beacon)
  • Integration tests for OpenAPI/docs endpoint
  • Integration tests for logging endpoints (/logs, /logs/configuration)
  • Integration tests for linux introspection plugins (launch_testing and Docker-based)
  • Port isolation per integration test via CMake-assigned unique ports
  • ROS_DOMAIN_ID isolation for integration tests

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged ros2_medkit_integration_tests at Robotics Stack Exchange

No version for distro kilted showing humble. Known supported distros are highlighted in the buttons above.

Package Summary

Version 0.7.2
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/selfpatch/ros2_medkit.git
VCS Type git
VCS Version main
Last Updated 2026-11-22
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Integration tests and demo nodes for ros2_medkit

Maintainers

  • bburda

Authors

No additional authors.

ros2_medkit_integration_tests

Integration tests, demo nodes, and shared test utilities for ros2_medkit.

Overview

This package contains everything needed to validate the ros2_medkit system end-to-end:

  • Demo nodes – automotive-themed C++ nodes (sensors, actuators, services, actions) that produce realistic ROS 2 traffic for testing
  • Feature tests – focused tests that validate individual API features (data access, operations, faults, SSE, CORS, auth, etc.)
  • Scenario tests – end-to-end stories that exercise multi-step workflows (fault lifecycle, action execution, discovery modes, subscriptions, etc.)
  • Shared test library (ros2_medkit_test_utils) – base test case, launch helpers, and assertion utilities shared across all test files

Package Structure

ros2_medkit_integration_tests/
  demo_nodes/           # C++ demo node sources
  launch/               # demo_nodes.launch.py
  ros2_medkit_test_utils/
    __init__.py
    constants.py        # DEFAULT_PORT, timeouts
    coverage.py         # GCOV_PREFIX helpers for CI
    gateway_test_case.py  # GatewayTestCase base class
    launch_helpers.py   # create_test_launch(), DEMO_NODE_REGISTRY
  test/
    features/           # Focused API feature tests
    scenarios/          # End-to-end workflow tests

Running Tests

# Build everything
colcon build --symlink-install
source install/setup.bash

# All integration tests
colcon test --packages-select ros2_medkit_integration_tests
colcon test-result --verbose

# Single test
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -R test_data_read

# Feature tests only
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -L feature

# Scenario tests only
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -L scenario

Demo Nodes

Launch all demo nodes for manual testing or the web UI:

ros2 launch ros2_medkit_integration_tests demo_nodes.launch.py

Node Namespace Type Description
temp_sensor /powertrain/engine Publisher Engine temperature (2 Hz)
rpm_sensor /powertrain/engine Publisher RPM readings (2 Hz)
pressure_sensor /chassis/brakes Publisher Brake pressure (2 Hz)
status_sensor /body/door/front_left Publisher Door open/closed (0.5 Hz)
lidar_sensor /perception/lidar Publisher + Fault reporter LaserScan with fault detection
actuator /chassis/brakes Subscriber + Publisher Brake actuator (command/feedback)
controller /body/lights Subscriber + Publisher Light controller (command/status)
calibration /powertrain/engine Service Trigger-based calibration
long_calibration /powertrain/engine Action Fibonacci-based long-running action
dual_calibration /testrig/dual Services + Actions left/calibrate and right/calibrate, left/sweep and right/sweep - one provider carrying each operation short name twice, so the ROS path is the only id that separates the copies

Crash reports

Every demo binary installs a fatal-signal handler before anything else runs. Most get it from run_demo_node() in include/ros2_medkit_integration_tests/demo_node_main.hpp; the two that cannot use that helper - unresponsive_param_node and managed_lifecycle_node, which own their shutdown sequence - call install_crash_backtrace() themselves. A node killed by SIGSEGV, SIGBUS or SIGABRT writes its stack to stderr, so launch_testing captures it with the rest of the process output:

MEDKIT-CRASH signal=SIGSEGV
/path/to/demo_brake_pressure_sensor(+0x129cb) [0x5603199349cb]
/opt/ros/<distro>/lib/libfastdds.so.3(...) [0x...]
MEDKIT-CRASH end

Grep a CI log for MEDKIT-CRASH to find one. Frames from our own binaries come back as binary(+0xOFFSET) because the release build has no exported symbols; resolve them with addr2line -e <binary> <offset>. The process still dies from

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package ros2_medkit_integration_tests

0.7.2 (2026-11-19)

  • The package builds as a binary package again. topics_test_plugin and its lookup of ros2_medkit_gateway are inside BUILD_TESTING, because the gateway is a test_depend. 0.7.1 failed to build on the buildfarm for Jazzy and Lyrical (#805). The binary package no longer installs topics_test_plugin (#806)
  • Contributors: \@mfaferek93

0.7.1 (2026-11-18)

  • Test only: coverage for recording manifests and per-file downloads, the gateway's helper nodes, fault lists on a chain of gateways, trigger and subscription paths, and steadier timing in the launch tests
  • Contributors: \@bburda, \@mfaferek93

0.7.0 (2026-08-27)

  • Every integration launch test runs on its own DDS domain, taken when the test starts and held through an open socket for exactly as long as it runs, so a crash or a SIGKILL releases it the same way an ordinary exit does. This replaces the hand-maintained per-package domain pools, which had to stay pairwise disjoint because colcon runs one ctest per package in parallel and a CTest RESOURCE_LOCK binds only inside a single ctest run (#551, #597)
  • Feature tests are registered by glob: a file dropped into test/features/*.test.py is registered with its port and domain assigned automatically, so no explicit registration is needed and none can bypass GATEWAY_TEST_PORT
  • Inline gateways and fault managers go through the shared launch helpers rather than each test hand-building its own, which also fixed the SIGKILL these tests hit under coverage instrumentation (#554)
  • The Python in this package is linted (#598), and the package is instrumented for coverage (#582)
  • Flaky suites are fixed at their cause rather than retried: the OPC UA Alarms and Conditions test, the action-status and diagnostic-bridge fault paths, the operation-handlers fixture, type_info caching and the documentation linkcheck (#504, #636)
  • Contributors: \@bburda, \@mfaferek93, \@YueBit

0.6.0 (2026-06-22)

  • New suites covering the SOVD entity status endpoints (REQ_INTEROP_076), lifecycle-aware app and component status (#455), and fault-storm capture liveness under bounded concurrency (#456)
  • Contributors: \@bburda

0.5.0 (2026-06-08)

  • New peer-aggregation suites: peer aggregation, cross-ECU fan-out across all resource types, daisy-chain hierarchical aggregation, leaf-collision aggregation, and cross-ECU log aggregation
  • New SOVD-aligned entity-model suites: runtime entity model, flat entity tree without areas, hybrid suppression, and per-entity fault scope isolation
  • New OpenAPI conformance suites: test_openapi_callability and test_openapi_response_drift validate the published spec against live responses
  • New graph-event discovery suite covering rclcpp graph-event driven discovery refresh
  • Coverage for the GET /apps/{id}/belongs-to discovery endpoint, nested x-medkit vendor payloads (#385), version-info aggregation, and pending-after-register update status (#378)
  • Tests: centralized ROS_DOMAIN_ID allocation and widened shutdown timeouts for sanitizer overhead
  • Contributors: \@bburda, \@eclipse0922

0.4.0 (2026-03-20)

  • Integration tests for SOVD resource locking (acquire, release, extend, fault clear with locks, expiration, parent propagation)
  • Integration tests for SOVD script execution endpoints (all formats, params, output, failure, lifecycle)
  • Integration tests for graph provider plugin (external plugin loading, entity introspection)
  • Integration tests for beacon discovery plugins (topic beacon, parameter beacon)
  • Integration tests for OpenAPI/docs endpoint
  • Integration tests for logging endpoints (/logs, /logs/configuration)
  • Integration tests for linux introspection plugins (launch_testing and Docker-based)
  • Port isolation per integration test via CMake-assigned unique ports
  • ROS_DOMAIN_ID isolation for integration tests

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged ros2_medkit_integration_tests at Robotics Stack Exchange

Package Summary

Version 0.7.2
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/selfpatch/ros2_medkit.git
VCS Type git
VCS Version main
Last Updated 2026-11-22
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Integration tests and demo nodes for ros2_medkit

Maintainers

  • bburda

Authors

No additional authors.

ros2_medkit_integration_tests

Integration tests, demo nodes, and shared test utilities for ros2_medkit.

Overview

This package contains everything needed to validate the ros2_medkit system end-to-end:

  • Demo nodes – automotive-themed C++ nodes (sensors, actuators, services, actions) that produce realistic ROS 2 traffic for testing
  • Feature tests – focused tests that validate individual API features (data access, operations, faults, SSE, CORS, auth, etc.)
  • Scenario tests – end-to-end stories that exercise multi-step workflows (fault lifecycle, action execution, discovery modes, subscriptions, etc.)
  • Shared test library (ros2_medkit_test_utils) – base test case, launch helpers, and assertion utilities shared across all test files

Package Structure

ros2_medkit_integration_tests/
  demo_nodes/           # C++ demo node sources
  launch/               # demo_nodes.launch.py
  ros2_medkit_test_utils/
    __init__.py
    constants.py        # DEFAULT_PORT, timeouts
    coverage.py         # GCOV_PREFIX helpers for CI
    gateway_test_case.py  # GatewayTestCase base class
    launch_helpers.py   # create_test_launch(), DEMO_NODE_REGISTRY
  test/
    features/           # Focused API feature tests
    scenarios/          # End-to-end workflow tests

Running Tests

# Build everything
colcon build --symlink-install
source install/setup.bash

# All integration tests
colcon test --packages-select ros2_medkit_integration_tests
colcon test-result --verbose

# Single test
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -R test_data_read

# Feature tests only
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -L feature

# Scenario tests only
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -L scenario

Demo Nodes

Launch all demo nodes for manual testing or the web UI:

ros2 launch ros2_medkit_integration_tests demo_nodes.launch.py

Node Namespace Type Description
temp_sensor /powertrain/engine Publisher Engine temperature (2 Hz)
rpm_sensor /powertrain/engine Publisher RPM readings (2 Hz)
pressure_sensor /chassis/brakes Publisher Brake pressure (2 Hz)
status_sensor /body/door/front_left Publisher Door open/closed (0.5 Hz)
lidar_sensor /perception/lidar Publisher + Fault reporter LaserScan with fault detection
actuator /chassis/brakes Subscriber + Publisher Brake actuator (command/feedback)
controller /body/lights Subscriber + Publisher Light controller (command/status)
calibration /powertrain/engine Service Trigger-based calibration
long_calibration /powertrain/engine Action Fibonacci-based long-running action
dual_calibration /testrig/dual Services + Actions left/calibrate and right/calibrate, left/sweep and right/sweep - one provider carrying each operation short name twice, so the ROS path is the only id that separates the copies

Crash reports

Every demo binary installs a fatal-signal handler before anything else runs. Most get it from run_demo_node() in include/ros2_medkit_integration_tests/demo_node_main.hpp; the two that cannot use that helper - unresponsive_param_node and managed_lifecycle_node, which own their shutdown sequence - call install_crash_backtrace() themselves. A node killed by SIGSEGV, SIGBUS or SIGABRT writes its stack to stderr, so launch_testing captures it with the rest of the process output:

MEDKIT-CRASH signal=SIGSEGV
/path/to/demo_brake_pressure_sensor(+0x129cb) [0x5603199349cb]
/opt/ros/<distro>/lib/libfastdds.so.3(...) [0x...]
MEDKIT-CRASH end

Grep a CI log for MEDKIT-CRASH to find one. Frames from our own binaries come back as binary(+0xOFFSET) because the release build has no exported symbols; resolve them with addr2line -e <binary> <offset>. The process still dies from

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package ros2_medkit_integration_tests

0.7.2 (2026-11-19)

  • The package builds as a binary package again. topics_test_plugin and its lookup of ros2_medkit_gateway are inside BUILD_TESTING, because the gateway is a test_depend. 0.7.1 failed to build on the buildfarm for Jazzy and Lyrical (#805). The binary package no longer installs topics_test_plugin (#806)
  • Contributors: \@mfaferek93

0.7.1 (2026-11-18)

  • Test only: coverage for recording manifests and per-file downloads, the gateway's helper nodes, fault lists on a chain of gateways, trigger and subscription paths, and steadier timing in the launch tests
  • Contributors: \@bburda, \@mfaferek93

0.7.0 (2026-08-27)

  • Every integration launch test runs on its own DDS domain, taken when the test starts and held through an open socket for exactly as long as it runs, so a crash or a SIGKILL releases it the same way an ordinary exit does. This replaces the hand-maintained per-package domain pools, which had to stay pairwise disjoint because colcon runs one ctest per package in parallel and a CTest RESOURCE_LOCK binds only inside a single ctest run (#551, #597)
  • Feature tests are registered by glob: a file dropped into test/features/*.test.py is registered with its port and domain assigned automatically, so no explicit registration is needed and none can bypass GATEWAY_TEST_PORT
  • Inline gateways and fault managers go through the shared launch helpers rather than each test hand-building its own, which also fixed the SIGKILL these tests hit under coverage instrumentation (#554)
  • The Python in this package is linted (#598), and the package is instrumented for coverage (#582)
  • Flaky suites are fixed at their cause rather than retried: the OPC UA Alarms and Conditions test, the action-status and diagnostic-bridge fault paths, the operation-handlers fixture, type_info caching and the documentation linkcheck (#504, #636)
  • Contributors: \@bburda, \@mfaferek93, \@YueBit

0.6.0 (2026-06-22)

  • New suites covering the SOVD entity status endpoints (REQ_INTEROP_076), lifecycle-aware app and component status (#455), and fault-storm capture liveness under bounded concurrency (#456)
  • Contributors: \@bburda

0.5.0 (2026-06-08)

  • New peer-aggregation suites: peer aggregation, cross-ECU fan-out across all resource types, daisy-chain hierarchical aggregation, leaf-collision aggregation, and cross-ECU log aggregation
  • New SOVD-aligned entity-model suites: runtime entity model, flat entity tree without areas, hybrid suppression, and per-entity fault scope isolation
  • New OpenAPI conformance suites: test_openapi_callability and test_openapi_response_drift validate the published spec against live responses
  • New graph-event discovery suite covering rclcpp graph-event driven discovery refresh
  • Coverage for the GET /apps/{id}/belongs-to discovery endpoint, nested x-medkit vendor payloads (#385), version-info aggregation, and pending-after-register update status (#378)
  • Tests: centralized ROS_DOMAIN_ID allocation and widened shutdown timeouts for sanitizer overhead
  • Contributors: \@bburda, \@eclipse0922

0.4.0 (2026-03-20)

  • Integration tests for SOVD resource locking (acquire, release, extend, fault clear with locks, expiration, parent propagation)
  • Integration tests for SOVD script execution endpoints (all formats, params, output, failure, lifecycle)
  • Integration tests for graph provider plugin (external plugin loading, entity introspection)
  • Integration tests for beacon discovery plugins (topic beacon, parameter beacon)
  • Integration tests for OpenAPI/docs endpoint
  • Integration tests for logging endpoints (/logs, /logs/configuration)
  • Integration tests for linux introspection plugins (launch_testing and Docker-based)
  • Port isolation per integration test via CMake-assigned unique ports
  • ROS_DOMAIN_ID isolation for integration tests

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged ros2_medkit_integration_tests at Robotics Stack Exchange

No version for distro rolling showing humble. Known supported distros are highlighted in the buttons above.

Package Summary

Version 0.7.2
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/selfpatch/ros2_medkit.git
VCS Type git
VCS Version main
Last Updated 2026-11-22
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Integration tests and demo nodes for ros2_medkit

Maintainers

  • bburda

Authors

No additional authors.

ros2_medkit_integration_tests

Integration tests, demo nodes, and shared test utilities for ros2_medkit.

Overview

This package contains everything needed to validate the ros2_medkit system end-to-end:

  • Demo nodes – automotive-themed C++ nodes (sensors, actuators, services, actions) that produce realistic ROS 2 traffic for testing
  • Feature tests – focused tests that validate individual API features (data access, operations, faults, SSE, CORS, auth, etc.)
  • Scenario tests – end-to-end stories that exercise multi-step workflows (fault lifecycle, action execution, discovery modes, subscriptions, etc.)
  • Shared test library (ros2_medkit_test_utils) – base test case, launch helpers, and assertion utilities shared across all test files

Package Structure

ros2_medkit_integration_tests/
  demo_nodes/           # C++ demo node sources
  launch/               # demo_nodes.launch.py
  ros2_medkit_test_utils/
    __init__.py
    constants.py        # DEFAULT_PORT, timeouts
    coverage.py         # GCOV_PREFIX helpers for CI
    gateway_test_case.py  # GatewayTestCase base class
    launch_helpers.py   # create_test_launch(), DEMO_NODE_REGISTRY
  test/
    features/           # Focused API feature tests
    scenarios/          # End-to-end workflow tests

Running Tests

# Build everything
colcon build --symlink-install
source install/setup.bash

# All integration tests
colcon test --packages-select ros2_medkit_integration_tests
colcon test-result --verbose

# Single test
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -R test_data_read

# Feature tests only
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -L feature

# Scenario tests only
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -L scenario

Demo Nodes

Launch all demo nodes for manual testing or the web UI:

ros2 launch ros2_medkit_integration_tests demo_nodes.launch.py

Node Namespace Type Description
temp_sensor /powertrain/engine Publisher Engine temperature (2 Hz)
rpm_sensor /powertrain/engine Publisher RPM readings (2 Hz)
pressure_sensor /chassis/brakes Publisher Brake pressure (2 Hz)
status_sensor /body/door/front_left Publisher Door open/closed (0.5 Hz)
lidar_sensor /perception/lidar Publisher + Fault reporter LaserScan with fault detection
actuator /chassis/brakes Subscriber + Publisher Brake actuator (command/feedback)
controller /body/lights Subscriber + Publisher Light controller (command/status)
calibration /powertrain/engine Service Trigger-based calibration
long_calibration /powertrain/engine Action Fibonacci-based long-running action
dual_calibration /testrig/dual Services + Actions left/calibrate and right/calibrate, left/sweep and right/sweep - one provider carrying each operation short name twice, so the ROS path is the only id that separates the copies

Crash reports

Every demo binary installs a fatal-signal handler before anything else runs. Most get it from run_demo_node() in include/ros2_medkit_integration_tests/demo_node_main.hpp; the two that cannot use that helper - unresponsive_param_node and managed_lifecycle_node, which own their shutdown sequence - call install_crash_backtrace() themselves. A node killed by SIGSEGV, SIGBUS or SIGABRT writes its stack to stderr, so launch_testing captures it with the rest of the process output:

MEDKIT-CRASH signal=SIGSEGV
/path/to/demo_brake_pressure_sensor(+0x129cb) [0x5603199349cb]
/opt/ros/<distro>/lib/libfastdds.so.3(...) [0x...]
MEDKIT-CRASH end

Grep a CI log for MEDKIT-CRASH to find one. Frames from our own binaries come back as binary(+0xOFFSET) because the release build has no exported symbols; resolve them with addr2line -e <binary> <offset>. The process still dies from

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package ros2_medkit_integration_tests

0.7.2 (2026-11-19)

  • The package builds as a binary package again. topics_test_plugin and its lookup of ros2_medkit_gateway are inside BUILD_TESTING, because the gateway is a test_depend. 0.7.1 failed to build on the buildfarm for Jazzy and Lyrical (#805). The binary package no longer installs topics_test_plugin (#806)
  • Contributors: \@mfaferek93

0.7.1 (2026-11-18)

  • Test only: coverage for recording manifests and per-file downloads, the gateway's helper nodes, fault lists on a chain of gateways, trigger and subscription paths, and steadier timing in the launch tests
  • Contributors: \@bburda, \@mfaferek93

0.7.0 (2026-08-27)

  • Every integration launch test runs on its own DDS domain, taken when the test starts and held through an open socket for exactly as long as it runs, so a crash or a SIGKILL releases it the same way an ordinary exit does. This replaces the hand-maintained per-package domain pools, which had to stay pairwise disjoint because colcon runs one ctest per package in parallel and a CTest RESOURCE_LOCK binds only inside a single ctest run (#551, #597)
  • Feature tests are registered by glob: a file dropped into test/features/*.test.py is registered with its port and domain assigned automatically, so no explicit registration is needed and none can bypass GATEWAY_TEST_PORT
  • Inline gateways and fault managers go through the shared launch helpers rather than each test hand-building its own, which also fixed the SIGKILL these tests hit under coverage instrumentation (#554)
  • The Python in this package is linted (#598), and the package is instrumented for coverage (#582)
  • Flaky suites are fixed at their cause rather than retried: the OPC UA Alarms and Conditions test, the action-status and diagnostic-bridge fault paths, the operation-handlers fixture, type_info caching and the documentation linkcheck (#504, #636)
  • Contributors: \@bburda, \@mfaferek93, \@YueBit

0.6.0 (2026-06-22)

  • New suites covering the SOVD entity status endpoints (REQ_INTEROP_076), lifecycle-aware app and component status (#455), and fault-storm capture liveness under bounded concurrency (#456)
  • Contributors: \@bburda

0.5.0 (2026-06-08)

  • New peer-aggregation suites: peer aggregation, cross-ECU fan-out across all resource types, daisy-chain hierarchical aggregation, leaf-collision aggregation, and cross-ECU log aggregation
  • New SOVD-aligned entity-model suites: runtime entity model, flat entity tree without areas, hybrid suppression, and per-entity fault scope isolation
  • New OpenAPI conformance suites: test_openapi_callability and test_openapi_response_drift validate the published spec against live responses
  • New graph-event discovery suite covering rclcpp graph-event driven discovery refresh
  • Coverage for the GET /apps/{id}/belongs-to discovery endpoint, nested x-medkit vendor payloads (#385), version-info aggregation, and pending-after-register update status (#378)
  • Tests: centralized ROS_DOMAIN_ID allocation and widened shutdown timeouts for sanitizer overhead
  • Contributors: \@bburda, \@eclipse0922

0.4.0 (2026-03-20)

  • Integration tests for SOVD resource locking (acquire, release, extend, fault clear with locks, expiration, parent propagation)
  • Integration tests for SOVD script execution endpoints (all formats, params, output, failure, lifecycle)
  • Integration tests for graph provider plugin (external plugin loading, entity introspection)
  • Integration tests for beacon discovery plugins (topic beacon, parameter beacon)
  • Integration tests for OpenAPI/docs endpoint
  • Integration tests for logging endpoints (/logs, /logs/configuration)
  • Integration tests for linux introspection plugins (launch_testing and Docker-based)
  • Port isolation per integration test via CMake-assigned unique ports
  • ROS_DOMAIN_ID isolation for integration tests

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged ros2_medkit_integration_tests at Robotics Stack Exchange

No version for distro github showing humble. Known supported distros are highlighted in the buttons above.

Package Summary

Version 0.7.2
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/selfpatch/ros2_medkit.git
VCS Type git
VCS Version main
Last Updated 2026-11-22
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Integration tests and demo nodes for ros2_medkit

Maintainers

  • bburda

Authors

No additional authors.

ros2_medkit_integration_tests

Integration tests, demo nodes, and shared test utilities for ros2_medkit.

Overview

This package contains everything needed to validate the ros2_medkit system end-to-end:

  • Demo nodes – automotive-themed C++ nodes (sensors, actuators, services, actions) that produce realistic ROS 2 traffic for testing
  • Feature tests – focused tests that validate individual API features (data access, operations, faults, SSE, CORS, auth, etc.)
  • Scenario tests – end-to-end stories that exercise multi-step workflows (fault lifecycle, action execution, discovery modes, subscriptions, etc.)
  • Shared test library (ros2_medkit_test_utils) – base test case, launch helpers, and assertion utilities shared across all test files

Package Structure

ros2_medkit_integration_tests/
  demo_nodes/           # C++ demo node sources
  launch/               # demo_nodes.launch.py
  ros2_medkit_test_utils/
    __init__.py
    constants.py        # DEFAULT_PORT, timeouts
    coverage.py         # GCOV_PREFIX helpers for CI
    gateway_test_case.py  # GatewayTestCase base class
    launch_helpers.py   # create_test_launch(), DEMO_NODE_REGISTRY
  test/
    features/           # Focused API feature tests
    scenarios/          # End-to-end workflow tests

Running Tests

# Build everything
colcon build --symlink-install
source install/setup.bash

# All integration tests
colcon test --packages-select ros2_medkit_integration_tests
colcon test-result --verbose

# Single test
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -R test_data_read

# Feature tests only
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -L feature

# Scenario tests only
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -L scenario

Demo Nodes

Launch all demo nodes for manual testing or the web UI:

ros2 launch ros2_medkit_integration_tests demo_nodes.launch.py

Node Namespace Type Description
temp_sensor /powertrain/engine Publisher Engine temperature (2 Hz)
rpm_sensor /powertrain/engine Publisher RPM readings (2 Hz)
pressure_sensor /chassis/brakes Publisher Brake pressure (2 Hz)
status_sensor /body/door/front_left Publisher Door open/closed (0.5 Hz)
lidar_sensor /perception/lidar Publisher + Fault reporter LaserScan with fault detection
actuator /chassis/brakes Subscriber + Publisher Brake actuator (command/feedback)
controller /body/lights Subscriber + Publisher Light controller (command/status)
calibration /powertrain/engine Service Trigger-based calibration
long_calibration /powertrain/engine Action Fibonacci-based long-running action
dual_calibration /testrig/dual Services + Actions left/calibrate and right/calibrate, left/sweep and right/sweep - one provider carrying each operation short name twice, so the ROS path is the only id that separates the copies

Crash reports

Every demo binary installs a fatal-signal handler before anything else runs. Most get it from run_demo_node() in include/ros2_medkit_integration_tests/demo_node_main.hpp; the two that cannot use that helper - unresponsive_param_node and managed_lifecycle_node, which own their shutdown sequence - call install_crash_backtrace() themselves. A node killed by SIGSEGV, SIGBUS or SIGABRT writes its stack to stderr, so launch_testing captures it with the rest of the process output:

MEDKIT-CRASH signal=SIGSEGV
/path/to/demo_brake_pressure_sensor(+0x129cb) [0x5603199349cb]
/opt/ros/<distro>/lib/libfastdds.so.3(...) [0x...]
MEDKIT-CRASH end

Grep a CI log for MEDKIT-CRASH to find one. Frames from our own binaries come back as binary(+0xOFFSET) because the release build has no exported symbols; resolve them with addr2line -e <binary> <offset>. The process still dies from

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package ros2_medkit_integration_tests

0.7.2 (2026-11-19)

  • The package builds as a binary package again. topics_test_plugin and its lookup of ros2_medkit_gateway are inside BUILD_TESTING, because the gateway is a test_depend. 0.7.1 failed to build on the buildfarm for Jazzy and Lyrical (#805). The binary package no longer installs topics_test_plugin (#806)
  • Contributors: \@mfaferek93

0.7.1 (2026-11-18)

  • Test only: coverage for recording manifests and per-file downloads, the gateway's helper nodes, fault lists on a chain of gateways, trigger and subscription paths, and steadier timing in the launch tests
  • Contributors: \@bburda, \@mfaferek93

0.7.0 (2026-08-27)

  • Every integration launch test runs on its own DDS domain, taken when the test starts and held through an open socket for exactly as long as it runs, so a crash or a SIGKILL releases it the same way an ordinary exit does. This replaces the hand-maintained per-package domain pools, which had to stay pairwise disjoint because colcon runs one ctest per package in parallel and a CTest RESOURCE_LOCK binds only inside a single ctest run (#551, #597)
  • Feature tests are registered by glob: a file dropped into test/features/*.test.py is registered with its port and domain assigned automatically, so no explicit registration is needed and none can bypass GATEWAY_TEST_PORT
  • Inline gateways and fault managers go through the shared launch helpers rather than each test hand-building its own, which also fixed the SIGKILL these tests hit under coverage instrumentation (#554)
  • The Python in this package is linted (#598), and the package is instrumented for coverage (#582)
  • Flaky suites are fixed at their cause rather than retried: the OPC UA Alarms and Conditions test, the action-status and diagnostic-bridge fault paths, the operation-handlers fixture, type_info caching and the documentation linkcheck (#504, #636)
  • Contributors: \@bburda, \@mfaferek93, \@YueBit

0.6.0 (2026-06-22)

  • New suites covering the SOVD entity status endpoints (REQ_INTEROP_076), lifecycle-aware app and component status (#455), and fault-storm capture liveness under bounded concurrency (#456)
  • Contributors: \@bburda

0.5.0 (2026-06-08)

  • New peer-aggregation suites: peer aggregation, cross-ECU fan-out across all resource types, daisy-chain hierarchical aggregation, leaf-collision aggregation, and cross-ECU log aggregation
  • New SOVD-aligned entity-model suites: runtime entity model, flat entity tree without areas, hybrid suppression, and per-entity fault scope isolation
  • New OpenAPI conformance suites: test_openapi_callability and test_openapi_response_drift validate the published spec against live responses
  • New graph-event discovery suite covering rclcpp graph-event driven discovery refresh
  • Coverage for the GET /apps/{id}/belongs-to discovery endpoint, nested x-medkit vendor payloads (#385), version-info aggregation, and pending-after-register update status (#378)
  • Tests: centralized ROS_DOMAIN_ID allocation and widened shutdown timeouts for sanitizer overhead
  • Contributors: \@bburda, \@eclipse0922

0.4.0 (2026-03-20)

  • Integration tests for SOVD resource locking (acquire, release, extend, fault clear with locks, expiration, parent propagation)
  • Integration tests for SOVD script execution endpoints (all formats, params, output, failure, lifecycle)
  • Integration tests for graph provider plugin (external plugin loading, entity introspection)
  • Integration tests for beacon discovery plugins (topic beacon, parameter beacon)
  • Integration tests for OpenAPI/docs endpoint
  • Integration tests for logging endpoints (/logs, /logs/configuration)
  • Integration tests for linux introspection plugins (launch_testing and Docker-based)
  • Port isolation per integration test via CMake-assigned unique ports
  • ROS_DOMAIN_ID isolation for integration tests

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged ros2_medkit_integration_tests at Robotics Stack Exchange

No version for distro galactic showing humble. Known supported distros are highlighted in the buttons above.

Package Summary

Version 0.7.2
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/selfpatch/ros2_medkit.git
VCS Type git
VCS Version main
Last Updated 2026-11-22
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Integration tests and demo nodes for ros2_medkit

Maintainers

  • bburda

Authors

No additional authors.

ros2_medkit_integration_tests

Integration tests, demo nodes, and shared test utilities for ros2_medkit.

Overview

This package contains everything needed to validate the ros2_medkit system end-to-end:

  • Demo nodes – automotive-themed C++ nodes (sensors, actuators, services, actions) that produce realistic ROS 2 traffic for testing
  • Feature tests – focused tests that validate individual API features (data access, operations, faults, SSE, CORS, auth, etc.)
  • Scenario tests – end-to-end stories that exercise multi-step workflows (fault lifecycle, action execution, discovery modes, subscriptions, etc.)
  • Shared test library (ros2_medkit_test_utils) – base test case, launch helpers, and assertion utilities shared across all test files

Package Structure

ros2_medkit_integration_tests/
  demo_nodes/           # C++ demo node sources
  launch/               # demo_nodes.launch.py
  ros2_medkit_test_utils/
    __init__.py
    constants.py        # DEFAULT_PORT, timeouts
    coverage.py         # GCOV_PREFIX helpers for CI
    gateway_test_case.py  # GatewayTestCase base class
    launch_helpers.py   # create_test_launch(), DEMO_NODE_REGISTRY
  test/
    features/           # Focused API feature tests
    scenarios/          # End-to-end workflow tests

Running Tests

# Build everything
colcon build --symlink-install
source install/setup.bash

# All integration tests
colcon test --packages-select ros2_medkit_integration_tests
colcon test-result --verbose

# Single test
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -R test_data_read

# Feature tests only
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -L feature

# Scenario tests only
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -L scenario

Demo Nodes

Launch all demo nodes for manual testing or the web UI:

ros2 launch ros2_medkit_integration_tests demo_nodes.launch.py

Node Namespace Type Description
temp_sensor /powertrain/engine Publisher Engine temperature (2 Hz)
rpm_sensor /powertrain/engine Publisher RPM readings (2 Hz)
pressure_sensor /chassis/brakes Publisher Brake pressure (2 Hz)
status_sensor /body/door/front_left Publisher Door open/closed (0.5 Hz)
lidar_sensor /perception/lidar Publisher + Fault reporter LaserScan with fault detection
actuator /chassis/brakes Subscriber + Publisher Brake actuator (command/feedback)
controller /body/lights Subscriber + Publisher Light controller (command/status)
calibration /powertrain/engine Service Trigger-based calibration
long_calibration /powertrain/engine Action Fibonacci-based long-running action
dual_calibration /testrig/dual Services + Actions left/calibrate and right/calibrate, left/sweep and right/sweep - one provider carrying each operation short name twice, so the ROS path is the only id that separates the copies

Crash reports

Every demo binary installs a fatal-signal handler before anything else runs. Most get it from run_demo_node() in include/ros2_medkit_integration_tests/demo_node_main.hpp; the two that cannot use that helper - unresponsive_param_node and managed_lifecycle_node, which own their shutdown sequence - call install_crash_backtrace() themselves. A node killed by SIGSEGV, SIGBUS or SIGABRT writes its stack to stderr, so launch_testing captures it with the rest of the process output:

MEDKIT-CRASH signal=SIGSEGV
/path/to/demo_brake_pressure_sensor(+0x129cb) [0x5603199349cb]
/opt/ros/<distro>/lib/libfastdds.so.3(...) [0x...]
MEDKIT-CRASH end

Grep a CI log for MEDKIT-CRASH to find one. Frames from our own binaries come back as binary(+0xOFFSET) because the release build has no exported symbols; resolve them with addr2line -e <binary> <offset>. The process still dies from

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package ros2_medkit_integration_tests

0.7.2 (2026-11-19)

  • The package builds as a binary package again. topics_test_plugin and its lookup of ros2_medkit_gateway are inside BUILD_TESTING, because the gateway is a test_depend. 0.7.1 failed to build on the buildfarm for Jazzy and Lyrical (#805). The binary package no longer installs topics_test_plugin (#806)
  • Contributors: \@mfaferek93

0.7.1 (2026-11-18)

  • Test only: coverage for recording manifests and per-file downloads, the gateway's helper nodes, fault lists on a chain of gateways, trigger and subscription paths, and steadier timing in the launch tests
  • Contributors: \@bburda, \@mfaferek93

0.7.0 (2026-08-27)

  • Every integration launch test runs on its own DDS domain, taken when the test starts and held through an open socket for exactly as long as it runs, so a crash or a SIGKILL releases it the same way an ordinary exit does. This replaces the hand-maintained per-package domain pools, which had to stay pairwise disjoint because colcon runs one ctest per package in parallel and a CTest RESOURCE_LOCK binds only inside a single ctest run (#551, #597)
  • Feature tests are registered by glob: a file dropped into test/features/*.test.py is registered with its port and domain assigned automatically, so no explicit registration is needed and none can bypass GATEWAY_TEST_PORT
  • Inline gateways and fault managers go through the shared launch helpers rather than each test hand-building its own, which also fixed the SIGKILL these tests hit under coverage instrumentation (#554)
  • The Python in this package is linted (#598), and the package is instrumented for coverage (#582)
  • Flaky suites are fixed at their cause rather than retried: the OPC UA Alarms and Conditions test, the action-status and diagnostic-bridge fault paths, the operation-handlers fixture, type_info caching and the documentation linkcheck (#504, #636)
  • Contributors: \@bburda, \@mfaferek93, \@YueBit

0.6.0 (2026-06-22)

  • New suites covering the SOVD entity status endpoints (REQ_INTEROP_076), lifecycle-aware app and component status (#455), and fault-storm capture liveness under bounded concurrency (#456)
  • Contributors: \@bburda

0.5.0 (2026-06-08)

  • New peer-aggregation suites: peer aggregation, cross-ECU fan-out across all resource types, daisy-chain hierarchical aggregation, leaf-collision aggregation, and cross-ECU log aggregation
  • New SOVD-aligned entity-model suites: runtime entity model, flat entity tree without areas, hybrid suppression, and per-entity fault scope isolation
  • New OpenAPI conformance suites: test_openapi_callability and test_openapi_response_drift validate the published spec against live responses
  • New graph-event discovery suite covering rclcpp graph-event driven discovery refresh
  • Coverage for the GET /apps/{id}/belongs-to discovery endpoint, nested x-medkit vendor payloads (#385), version-info aggregation, and pending-after-register update status (#378)
  • Tests: centralized ROS_DOMAIN_ID allocation and widened shutdown timeouts for sanitizer overhead
  • Contributors: \@bburda, \@eclipse0922

0.4.0 (2026-03-20)

  • Integration tests for SOVD resource locking (acquire, release, extend, fault clear with locks, expiration, parent propagation)
  • Integration tests for SOVD script execution endpoints (all formats, params, output, failure, lifecycle)
  • Integration tests for graph provider plugin (external plugin loading, entity introspection)
  • Integration tests for beacon discovery plugins (topic beacon, parameter beacon)
  • Integration tests for OpenAPI/docs endpoint
  • Integration tests for logging endpoints (/logs, /logs/configuration)
  • Integration tests for linux introspection plugins (launch_testing and Docker-based)
  • Port isolation per integration test via CMake-assigned unique ports
  • ROS_DOMAIN_ID isolation for integration tests

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged ros2_medkit_integration_tests at Robotics Stack Exchange

No version for distro iron showing humble. Known supported distros are highlighted in the buttons above.

Package Summary

Version 0.7.2
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/selfpatch/ros2_medkit.git
VCS Type git
VCS Version main
Last Updated 2026-11-22
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Integration tests and demo nodes for ros2_medkit

Maintainers

  • bburda

Authors

No additional authors.

ros2_medkit_integration_tests

Integration tests, demo nodes, and shared test utilities for ros2_medkit.

Overview

This package contains everything needed to validate the ros2_medkit system end-to-end:

  • Demo nodes – automotive-themed C++ nodes (sensors, actuators, services, actions) that produce realistic ROS 2 traffic for testing
  • Feature tests – focused tests that validate individual API features (data access, operations, faults, SSE, CORS, auth, etc.)
  • Scenario tests – end-to-end stories that exercise multi-step workflows (fault lifecycle, action execution, discovery modes, subscriptions, etc.)
  • Shared test library (ros2_medkit_test_utils) – base test case, launch helpers, and assertion utilities shared across all test files

Package Structure

ros2_medkit_integration_tests/
  demo_nodes/           # C++ demo node sources
  launch/               # demo_nodes.launch.py
  ros2_medkit_test_utils/
    __init__.py
    constants.py        # DEFAULT_PORT, timeouts
    coverage.py         # GCOV_PREFIX helpers for CI
    gateway_test_case.py  # GatewayTestCase base class
    launch_helpers.py   # create_test_launch(), DEMO_NODE_REGISTRY
  test/
    features/           # Focused API feature tests
    scenarios/          # End-to-end workflow tests

Running Tests

# Build everything
colcon build --symlink-install
source install/setup.bash

# All integration tests
colcon test --packages-select ros2_medkit_integration_tests
colcon test-result --verbose

# Single test
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -R test_data_read

# Feature tests only
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -L feature

# Scenario tests only
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -L scenario

Demo Nodes

Launch all demo nodes for manual testing or the web UI:

ros2 launch ros2_medkit_integration_tests demo_nodes.launch.py

Node Namespace Type Description
temp_sensor /powertrain/engine Publisher Engine temperature (2 Hz)
rpm_sensor /powertrain/engine Publisher RPM readings (2 Hz)
pressure_sensor /chassis/brakes Publisher Brake pressure (2 Hz)
status_sensor /body/door/front_left Publisher Door open/closed (0.5 Hz)
lidar_sensor /perception/lidar Publisher + Fault reporter LaserScan with fault detection
actuator /chassis/brakes Subscriber + Publisher Brake actuator (command/feedback)
controller /body/lights Subscriber + Publisher Light controller (command/status)
calibration /powertrain/engine Service Trigger-based calibration
long_calibration /powertrain/engine Action Fibonacci-based long-running action
dual_calibration /testrig/dual Services + Actions left/calibrate and right/calibrate, left/sweep and right/sweep - one provider carrying each operation short name twice, so the ROS path is the only id that separates the copies

Crash reports

Every demo binary installs a fatal-signal handler before anything else runs. Most get it from run_demo_node() in include/ros2_medkit_integration_tests/demo_node_main.hpp; the two that cannot use that helper - unresponsive_param_node and managed_lifecycle_node, which own their shutdown sequence - call install_crash_backtrace() themselves. A node killed by SIGSEGV, SIGBUS or SIGABRT writes its stack to stderr, so launch_testing captures it with the rest of the process output:

MEDKIT-CRASH signal=SIGSEGV
/path/to/demo_brake_pressure_sensor(+0x129cb) [0x5603199349cb]
/opt/ros/<distro>/lib/libfastdds.so.3(...) [0x...]
MEDKIT-CRASH end

Grep a CI log for MEDKIT-CRASH to find one. Frames from our own binaries come back as binary(+0xOFFSET) because the release build has no exported symbols; resolve them with addr2line -e <binary> <offset>. The process still dies from

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package ros2_medkit_integration_tests

0.7.2 (2026-11-19)

  • The package builds as a binary package again. topics_test_plugin and its lookup of ros2_medkit_gateway are inside BUILD_TESTING, because the gateway is a test_depend. 0.7.1 failed to build on the buildfarm for Jazzy and Lyrical (#805). The binary package no longer installs topics_test_plugin (#806)
  • Contributors: \@mfaferek93

0.7.1 (2026-11-18)

  • Test only: coverage for recording manifests and per-file downloads, the gateway's helper nodes, fault lists on a chain of gateways, trigger and subscription paths, and steadier timing in the launch tests
  • Contributors: \@bburda, \@mfaferek93

0.7.0 (2026-08-27)

  • Every integration launch test runs on its own DDS domain, taken when the test starts and held through an open socket for exactly as long as it runs, so a crash or a SIGKILL releases it the same way an ordinary exit does. This replaces the hand-maintained per-package domain pools, which had to stay pairwise disjoint because colcon runs one ctest per package in parallel and a CTest RESOURCE_LOCK binds only inside a single ctest run (#551, #597)
  • Feature tests are registered by glob: a file dropped into test/features/*.test.py is registered with its port and domain assigned automatically, so no explicit registration is needed and none can bypass GATEWAY_TEST_PORT
  • Inline gateways and fault managers go through the shared launch helpers rather than each test hand-building its own, which also fixed the SIGKILL these tests hit under coverage instrumentation (#554)
  • The Python in this package is linted (#598), and the package is instrumented for coverage (#582)
  • Flaky suites are fixed at their cause rather than retried: the OPC UA Alarms and Conditions test, the action-status and diagnostic-bridge fault paths, the operation-handlers fixture, type_info caching and the documentation linkcheck (#504, #636)
  • Contributors: \@bburda, \@mfaferek93, \@YueBit

0.6.0 (2026-06-22)

  • New suites covering the SOVD entity status endpoints (REQ_INTEROP_076), lifecycle-aware app and component status (#455), and fault-storm capture liveness under bounded concurrency (#456)
  • Contributors: \@bburda

0.5.0 (2026-06-08)

  • New peer-aggregation suites: peer aggregation, cross-ECU fan-out across all resource types, daisy-chain hierarchical aggregation, leaf-collision aggregation, and cross-ECU log aggregation
  • New SOVD-aligned entity-model suites: runtime entity model, flat entity tree without areas, hybrid suppression, and per-entity fault scope isolation
  • New OpenAPI conformance suites: test_openapi_callability and test_openapi_response_drift validate the published spec against live responses
  • New graph-event discovery suite covering rclcpp graph-event driven discovery refresh
  • Coverage for the GET /apps/{id}/belongs-to discovery endpoint, nested x-medkit vendor payloads (#385), version-info aggregation, and pending-after-register update status (#378)
  • Tests: centralized ROS_DOMAIN_ID allocation and widened shutdown timeouts for sanitizer overhead
  • Contributors: \@bburda, \@eclipse0922

0.4.0 (2026-03-20)

  • Integration tests for SOVD resource locking (acquire, release, extend, fault clear with locks, expiration, parent propagation)
  • Integration tests for SOVD script execution endpoints (all formats, params, output, failure, lifecycle)
  • Integration tests for graph provider plugin (external plugin loading, entity introspection)
  • Integration tests for beacon discovery plugins (topic beacon, parameter beacon)
  • Integration tests for OpenAPI/docs endpoint
  • Integration tests for logging endpoints (/logs, /logs/configuration)
  • Integration tests for linux introspection plugins (launch_testing and Docker-based)
  • Port isolation per integration test via CMake-assigned unique ports
  • ROS_DOMAIN_ID isolation for integration tests

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged ros2_medkit_integration_tests at Robotics Stack Exchange

No version for distro melodic showing humble. Known supported distros are highlighted in the buttons above.

Package Summary

Version 0.7.2
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/selfpatch/ros2_medkit.git
VCS Type git
VCS Version main
Last Updated 2026-11-22
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Integration tests and demo nodes for ros2_medkit

Maintainers

  • bburda

Authors

No additional authors.

ros2_medkit_integration_tests

Integration tests, demo nodes, and shared test utilities for ros2_medkit.

Overview

This package contains everything needed to validate the ros2_medkit system end-to-end:

  • Demo nodes – automotive-themed C++ nodes (sensors, actuators, services, actions) that produce realistic ROS 2 traffic for testing
  • Feature tests – focused tests that validate individual API features (data access, operations, faults, SSE, CORS, auth, etc.)
  • Scenario tests – end-to-end stories that exercise multi-step workflows (fault lifecycle, action execution, discovery modes, subscriptions, etc.)
  • Shared test library (ros2_medkit_test_utils) – base test case, launch helpers, and assertion utilities shared across all test files

Package Structure

ros2_medkit_integration_tests/
  demo_nodes/           # C++ demo node sources
  launch/               # demo_nodes.launch.py
  ros2_medkit_test_utils/
    __init__.py
    constants.py        # DEFAULT_PORT, timeouts
    coverage.py         # GCOV_PREFIX helpers for CI
    gateway_test_case.py  # GatewayTestCase base class
    launch_helpers.py   # create_test_launch(), DEMO_NODE_REGISTRY
  test/
    features/           # Focused API feature tests
    scenarios/          # End-to-end workflow tests

Running Tests

# Build everything
colcon build --symlink-install
source install/setup.bash

# All integration tests
colcon test --packages-select ros2_medkit_integration_tests
colcon test-result --verbose

# Single test
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -R test_data_read

# Feature tests only
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -L feature

# Scenario tests only
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -L scenario

Demo Nodes

Launch all demo nodes for manual testing or the web UI:

ros2 launch ros2_medkit_integration_tests demo_nodes.launch.py

Node Namespace Type Description
temp_sensor /powertrain/engine Publisher Engine temperature (2 Hz)
rpm_sensor /powertrain/engine Publisher RPM readings (2 Hz)
pressure_sensor /chassis/brakes Publisher Brake pressure (2 Hz)
status_sensor /body/door/front_left Publisher Door open/closed (0.5 Hz)
lidar_sensor /perception/lidar Publisher + Fault reporter LaserScan with fault detection
actuator /chassis/brakes Subscriber + Publisher Brake actuator (command/feedback)
controller /body/lights Subscriber + Publisher Light controller (command/status)
calibration /powertrain/engine Service Trigger-based calibration
long_calibration /powertrain/engine Action Fibonacci-based long-running action
dual_calibration /testrig/dual Services + Actions left/calibrate and right/calibrate, left/sweep and right/sweep - one provider carrying each operation short name twice, so the ROS path is the only id that separates the copies

Crash reports

Every demo binary installs a fatal-signal handler before anything else runs. Most get it from run_demo_node() in include/ros2_medkit_integration_tests/demo_node_main.hpp; the two that cannot use that helper - unresponsive_param_node and managed_lifecycle_node, which own their shutdown sequence - call install_crash_backtrace() themselves. A node killed by SIGSEGV, SIGBUS or SIGABRT writes its stack to stderr, so launch_testing captures it with the rest of the process output:

MEDKIT-CRASH signal=SIGSEGV
/path/to/demo_brake_pressure_sensor(+0x129cb) [0x5603199349cb]
/opt/ros/<distro>/lib/libfastdds.so.3(...) [0x...]
MEDKIT-CRASH end

Grep a CI log for MEDKIT-CRASH to find one. Frames from our own binaries come back as binary(+0xOFFSET) because the release build has no exported symbols; resolve them with addr2line -e <binary> <offset>. The process still dies from

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package ros2_medkit_integration_tests

0.7.2 (2026-11-19)

  • The package builds as a binary package again. topics_test_plugin and its lookup of ros2_medkit_gateway are inside BUILD_TESTING, because the gateway is a test_depend. 0.7.1 failed to build on the buildfarm for Jazzy and Lyrical (#805). The binary package no longer installs topics_test_plugin (#806)
  • Contributors: \@mfaferek93

0.7.1 (2026-11-18)

  • Test only: coverage for recording manifests and per-file downloads, the gateway's helper nodes, fault lists on a chain of gateways, trigger and subscription paths, and steadier timing in the launch tests
  • Contributors: \@bburda, \@mfaferek93

0.7.0 (2026-08-27)

  • Every integration launch test runs on its own DDS domain, taken when the test starts and held through an open socket for exactly as long as it runs, so a crash or a SIGKILL releases it the same way an ordinary exit does. This replaces the hand-maintained per-package domain pools, which had to stay pairwise disjoint because colcon runs one ctest per package in parallel and a CTest RESOURCE_LOCK binds only inside a single ctest run (#551, #597)
  • Feature tests are registered by glob: a file dropped into test/features/*.test.py is registered with its port and domain assigned automatically, so no explicit registration is needed and none can bypass GATEWAY_TEST_PORT
  • Inline gateways and fault managers go through the shared launch helpers rather than each test hand-building its own, which also fixed the SIGKILL these tests hit under coverage instrumentation (#554)
  • The Python in this package is linted (#598), and the package is instrumented for coverage (#582)
  • Flaky suites are fixed at their cause rather than retried: the OPC UA Alarms and Conditions test, the action-status and diagnostic-bridge fault paths, the operation-handlers fixture, type_info caching and the documentation linkcheck (#504, #636)
  • Contributors: \@bburda, \@mfaferek93, \@YueBit

0.6.0 (2026-06-22)

  • New suites covering the SOVD entity status endpoints (REQ_INTEROP_076), lifecycle-aware app and component status (#455), and fault-storm capture liveness under bounded concurrency (#456)
  • Contributors: \@bburda

0.5.0 (2026-06-08)

  • New peer-aggregation suites: peer aggregation, cross-ECU fan-out across all resource types, daisy-chain hierarchical aggregation, leaf-collision aggregation, and cross-ECU log aggregation
  • New SOVD-aligned entity-model suites: runtime entity model, flat entity tree without areas, hybrid suppression, and per-entity fault scope isolation
  • New OpenAPI conformance suites: test_openapi_callability and test_openapi_response_drift validate the published spec against live responses
  • New graph-event discovery suite covering rclcpp graph-event driven discovery refresh
  • Coverage for the GET /apps/{id}/belongs-to discovery endpoint, nested x-medkit vendor payloads (#385), version-info aggregation, and pending-after-register update status (#378)
  • Tests: centralized ROS_DOMAIN_ID allocation and widened shutdown timeouts for sanitizer overhead
  • Contributors: \@bburda, \@eclipse0922

0.4.0 (2026-03-20)

  • Integration tests for SOVD resource locking (acquire, release, extend, fault clear with locks, expiration, parent propagation)
  • Integration tests for SOVD script execution endpoints (all formats, params, output, failure, lifecycle)
  • Integration tests for graph provider plugin (external plugin loading, entity introspection)
  • Integration tests for beacon discovery plugins (topic beacon, parameter beacon)
  • Integration tests for OpenAPI/docs endpoint
  • Integration tests for logging endpoints (/logs, /logs/configuration)
  • Integration tests for linux introspection plugins (launch_testing and Docker-based)
  • Port isolation per integration test via CMake-assigned unique ports
  • ROS_DOMAIN_ID isolation for integration tests

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged ros2_medkit_integration_tests at Robotics Stack Exchange

No version for distro noetic showing humble. Known supported distros are highlighted in the buttons above.

Package Summary

Version 0.7.2
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/selfpatch/ros2_medkit.git
VCS Type git
VCS Version main
Last Updated 2026-11-22
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Integration tests and demo nodes for ros2_medkit

Maintainers

  • bburda

Authors

No additional authors.

ros2_medkit_integration_tests

Integration tests, demo nodes, and shared test utilities for ros2_medkit.

Overview

This package contains everything needed to validate the ros2_medkit system end-to-end:

  • Demo nodes – automotive-themed C++ nodes (sensors, actuators, services, actions) that produce realistic ROS 2 traffic for testing
  • Feature tests – focused tests that validate individual API features (data access, operations, faults, SSE, CORS, auth, etc.)
  • Scenario tests – end-to-end stories that exercise multi-step workflows (fault lifecycle, action execution, discovery modes, subscriptions, etc.)
  • Shared test library (ros2_medkit_test_utils) – base test case, launch helpers, and assertion utilities shared across all test files

Package Structure

ros2_medkit_integration_tests/
  demo_nodes/           # C++ demo node sources
  launch/               # demo_nodes.launch.py
  ros2_medkit_test_utils/
    __init__.py
    constants.py        # DEFAULT_PORT, timeouts
    coverage.py         # GCOV_PREFIX helpers for CI
    gateway_test_case.py  # GatewayTestCase base class
    launch_helpers.py   # create_test_launch(), DEMO_NODE_REGISTRY
  test/
    features/           # Focused API feature tests
    scenarios/          # End-to-end workflow tests

Running Tests

# Build everything
colcon build --symlink-install
source install/setup.bash

# All integration tests
colcon test --packages-select ros2_medkit_integration_tests
colcon test-result --verbose

# Single test
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -R test_data_read

# Feature tests only
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -L feature

# Scenario tests only
colcon test --packages-select ros2_medkit_integration_tests \
  --ctest-args -L scenario

Demo Nodes

Launch all demo nodes for manual testing or the web UI:

ros2 launch ros2_medkit_integration_tests demo_nodes.launch.py

Node Namespace Type Description
temp_sensor /powertrain/engine Publisher Engine temperature (2 Hz)
rpm_sensor /powertrain/engine Publisher RPM readings (2 Hz)
pressure_sensor /chassis/brakes Publisher Brake pressure (2 Hz)
status_sensor /body/door/front_left Publisher Door open/closed (0.5 Hz)
lidar_sensor /perception/lidar Publisher + Fault reporter LaserScan with fault detection
actuator /chassis/brakes Subscriber + Publisher Brake actuator (command/feedback)
controller /body/lights Subscriber + Publisher Light controller (command/status)
calibration /powertrain/engine Service Trigger-based calibration
long_calibration /powertrain/engine Action Fibonacci-based long-running action
dual_calibration /testrig/dual Services + Actions left/calibrate and right/calibrate, left/sweep and right/sweep - one provider carrying each operation short name twice, so the ROS path is the only id that separates the copies

Crash reports

Every demo binary installs a fatal-signal handler before anything else runs. Most get it from run_demo_node() in include/ros2_medkit_integration_tests/demo_node_main.hpp; the two that cannot use that helper - unresponsive_param_node and managed_lifecycle_node, which own their shutdown sequence - call install_crash_backtrace() themselves. A node killed by SIGSEGV, SIGBUS or SIGABRT writes its stack to stderr, so launch_testing captures it with the rest of the process output:

MEDKIT-CRASH signal=SIGSEGV
/path/to/demo_brake_pressure_sensor(+0x129cb) [0x5603199349cb]
/opt/ros/<distro>/lib/libfastdds.so.3(...) [0x...]
MEDKIT-CRASH end

Grep a CI log for MEDKIT-CRASH to find one. Frames from our own binaries come back as binary(+0xOFFSET) because the release build has no exported symbols; resolve them with addr2line -e <binary> <offset>. The process still dies from

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package ros2_medkit_integration_tests

0.7.2 (2026-11-19)

  • The package builds as a binary package again. topics_test_plugin and its lookup of ros2_medkit_gateway are inside BUILD_TESTING, because the gateway is a test_depend. 0.7.1 failed to build on the buildfarm for Jazzy and Lyrical (#805). The binary package no longer installs topics_test_plugin (#806)
  • Contributors: \@mfaferek93

0.7.1 (2026-11-18)

  • Test only: coverage for recording manifests and per-file downloads, the gateway's helper nodes, fault lists on a chain of gateways, trigger and subscription paths, and steadier timing in the launch tests
  • Contributors: \@bburda, \@mfaferek93

0.7.0 (2026-08-27)

  • Every integration launch test runs on its own DDS domain, taken when the test starts and held through an open socket for exactly as long as it runs, so a crash or a SIGKILL releases it the same way an ordinary exit does. This replaces the hand-maintained per-package domain pools, which had to stay pairwise disjoint because colcon runs one ctest per package in parallel and a CTest RESOURCE_LOCK binds only inside a single ctest run (#551, #597)
  • Feature tests are registered by glob: a file dropped into test/features/*.test.py is registered with its port and domain assigned automatically, so no explicit registration is needed and none can bypass GATEWAY_TEST_PORT
  • Inline gateways and fault managers go through the shared launch helpers rather than each test hand-building its own, which also fixed the SIGKILL these tests hit under coverage instrumentation (#554)
  • The Python in this package is linted (#598), and the package is instrumented for coverage (#582)
  • Flaky suites are fixed at their cause rather than retried: the OPC UA Alarms and Conditions test, the action-status and diagnostic-bridge fault paths, the operation-handlers fixture, type_info caching and the documentation linkcheck (#504, #636)
  • Contributors: \@bburda, \@mfaferek93, \@YueBit

0.6.0 (2026-06-22)

  • New suites covering the SOVD entity status endpoints (REQ_INTEROP_076), lifecycle-aware app and component status (#455), and fault-storm capture liveness under bounded concurrency (#456)
  • Contributors: \@bburda

0.5.0 (2026-06-08)

  • New peer-aggregation suites: peer aggregation, cross-ECU fan-out across all resource types, daisy-chain hierarchical aggregation, leaf-collision aggregation, and cross-ECU log aggregation
  • New SOVD-aligned entity-model suites: runtime entity model, flat entity tree without areas, hybrid suppression, and per-entity fault scope isolation
  • New OpenAPI conformance suites: test_openapi_callability and test_openapi_response_drift validate the published spec against live responses
  • New graph-event discovery suite covering rclcpp graph-event driven discovery refresh
  • Coverage for the GET /apps/{id}/belongs-to discovery endpoint, nested x-medkit vendor payloads (#385), version-info aggregation, and pending-after-register update status (#378)
  • Tests: centralized ROS_DOMAIN_ID allocation and widened shutdown timeouts for sanitizer overhead
  • Contributors: \@bburda, \@eclipse0922

0.4.0 (2026-03-20)

  • Integration tests for SOVD resource locking (acquire, release, extend, fault clear with locks, expiration, parent propagation)
  • Integration tests for SOVD script execution endpoints (all formats, params, output, failure, lifecycle)
  • Integration tests for graph provider plugin (external plugin loading, entity introspection)
  • Integration tests for beacon discovery plugins (topic beacon, parameter beacon)
  • Integration tests for OpenAPI/docs endpoint
  • Integration tests for logging endpoints (/logs, /logs/configuration)
  • Integration tests for linux introspection plugins (launch_testing and Docker-based)
  • Port isolation per integration test via CMake-assigned unique ports
  • ROS_DOMAIN_ID isolation for integration tests

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged ros2_medkit_integration_tests at Robotics Stack Exchange