The unit tests for the legacy bindings cannot be used directly with the new bindings, so they have currently been moved to tests/deprecated.
There are also unit tests for the new bindings under pytests.
However, it is unclear whether these new tests cover all the functionality previously tested by the legacy unit tests.
Another option would be to update the legacy binding tests. This would mainly involve:
• Adding bindings for additional OMPL classes (e.g., StatePropagator, which is used in the legacy test_control.py).
• Updating outdated syntax, such as replacing goal()[0] = env.goal[0] with goal[0] = env.goal[0].
The unit tests for the legacy bindings cannot be used directly with the new bindings, so they have currently been moved to tests/deprecated.
There are also unit tests for the new bindings under
pytests.However, it is unclear whether these new tests cover all the functionality previously tested by the legacy unit tests.
Another option would be to update the legacy binding tests. This would mainly involve:
• Adding bindings for additional OMPL classes (e.g.,
StatePropagator, which is used in the legacytest_control.py).• Updating outdated syntax, such as replacing
goal()[0] = env.goal[0]withgoal[0] = env.goal[0].