simulator_compatibility_test

Purpose

Test procedures (e.g. test codes) to check whether a certain simulator is compatible with Autoware

Overview of the test codes

File structure

• test_base
• test_sim_common_manual_testing
• test_morai_sim

1. test_base provides shared methods for testing. Other test codes are created based on functions defined here.
2. test_sim_common_manual_testing provides the most basic functions. Any simulator can be tested using codes here. However, to make these codes usable with any simulators, the codes do not include any features for test automation.
3. test_morai_sim is an automated version of test_sim_common_manual_testing for MORAI SIM: Drive. Thus it includes ‘MORAI SIM: Drive’-specific codes. Users of the other simulators may create similar version for their simulator of interest.

Test Procedures for test_sim_common_manual_testing

Build process before test

source install/setup.bash
colcon build --packages-select simulator_compatibility_test
cd src/universe/autoware.universe/tools/simulator_test/simulator_compatibility_test/test_sim_common_manual_testing

To run each test case manually

Test Case #1

1. Run your simulator
2. Load a map and an ego vehicle for the test
3. Run the test using the following command

   python -m pytest test_01_control_mode_and_report.py
   

1. Check if expected behavior is created within the simulator
   • Ego vehicle control mode is changed into Manual (If the simulator has a GUI for this one, it should display the ego is in Manual)
   • Ego vehicle control mode is changed into Auto (If the simulator has a GUI for this one, it should display the ego is in Auto)
2. Check if pytest output is passed or failure

Test Case #2

1. Run your simulator (If the simulator is already running, skip this part)
2. Load a map and an ego vehicle for the test (If a map and an ego are loaded already, skip this part)
3. Run the test using the following command

   python -m pytest test_02_change_gear_and_report.py
   

1. Check if expected behavior is created within the simulator
   • Ego vehicle gear mode is changed into “P” (If the simulator has a GUI for this one, it should display the gear mode is in “P”)
   • Ego vehicle gear mode is changed into “N” (If the simulator has a GUI for this one, it should display the gear mode is in “N”)
   • Ego vehicle gear mode is changed into “R” (If the simulator has a GUI for this one, it should display the gear mode is in “R”)
   • Ego vehicle gear mode is changed into “D” (If the simulator has a GUI for this one, it should display the gear mode is in “D”)
2. Check if pytest output is passed or failure

Test Case #3

1. Run your simulator (If the simulator is already running, skip this part)
2. Load a map and an ego vehicle for the test (If a map and an ego are loaded already, skip this part)
3. Run the test using the following command

   python -m pytest test_03_longitudinal_command_and_report.py
   

1. Check if expected behavior is created within the simulator
   • Ego vehicle longitudinal velocity is greater than 10 kph (If the simulator has a GUI for this one, it should display the longitudinal velocity is greater than 10 kph)
   • Ego vehicle longitudinal velocity is going below 10 kph. This is an ego vehicle initialize process to ensure the following acceleration is made by longitudinal.acceleration value (If the simulator has a GUI for this one, it should display the longitudinal velocity is less than 10 kph)
   • Ego vehicle longitudinal velocity is greater than 10 kph (If the simulator has a GUI for this one, it should display the longitudinal velocity is greater than 10 kph)
   • Ego vehicle longitudinal velocity is going below 10 kph. This is an ego vehicle reset process to tear down this test case.
2. Check if pytest output is passed or failure

Test Case #4

1. Run your simulator (If the simulator is already running, skip this part)
2. Load a map and an ego vehicle for the test (If a map and an ego are loaded already, skip this part)
3. Run the test using the following command

   python -m pytest test_04_lateral_command_and_report.py
   

1. Check if expected behavior is created within the simulator
   • Ego vehicle steering and/or tire value is greater than 0 degree (If the simulator has a GUI for this one, it should display the steering and/or tire is greater than 0 degree)
   • Ego vehicle steering and/or tire value is 0 degree. This is a reset process. (If the simulator has a GUI for this one, it should display the steering and/or tire is 0 degree)
   • Ego vehicle steering and/or tire value is less than 0 degree (If the simulator has a GUI for this one, it should display the steering and/or tire is less than 0 degree)
   • Ego vehicle steering and/or tire value is 0 degree. This is a reset process. (If the simulator has a GUI for this one, it should display the steering and/or tire is 0 degree)
2. Check if pytest output is passed or failure

Test Case #5

1. Run your simulator (If the simulator is already running, skip this part)
2. Load a map and an ego vehicle for the test (If a map and an ego are loaded already, skip this part)

File truncated at 100 lines see the full file

Changelog for package simulator_compatibility_test

0.3.0 (2025-08-11)

0.2.0 (2025-03-24)

0.1.0 (2025-01-28)

• fix: autoware_msgs (#68)

• feat(simulator_compatibility_test): temporariy remove tests for control_mode_command (#34)

• feat!: change from autoware_auto_msgs to autoware_msgs (#30)

  • feat!: replace autoware_auto_msgs with autoware_msgs
  • style(pre-commit): autofix
  • feat: port remaining autoware_auto_msgs to autoware_msgs (#32)
  • feat: port remaining autoware_auto_msgs to autoware_msgs

  * style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>

  • remove <depend>autoware_msgs</depend>

  * remove non-existent dep ---------Co-authored-by: mitsudome-r <<ryohsuke.mitsudome@tier4.jp>> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Ryohsuke Mitsudome <<43976834+mitsudome-r@users.noreply.github.com>> Co-authored-by: M. Fatih Cırıt <<mfc@leodrive.ai>>

• feat: move tools from autoware.universe (#8)

  • feat: move tools from autoware.universe
  • update build_depends.repos

  * update build_depends.repos ---------

• Contributors: Kosuke Takeuchi, Ryohsuke Mitsudome, Takayuki Murooka, Yukihiro Saito