Skip to content

remove random movement test - #129

Merged
energy-in-joles merged 1 commit into
mainfrom
remove_random
Jun 3, 2026
Merged

energy-in-joles merged 1 commit into
mainfrom
remove_random

Conversation

@energy-in-joles

Copy link
Copy Markdown
Member

No description provided.

Copilot AI review requested due to automatic review settings June 3, 2026 22:20
@energy-in-joles
energy-in-joles merged commit 7ec2b98 into main Jun 3, 2026
3 checks passed
@energy-in-joles
energy-in-joles deleted the remove_random branch June 3, 2026 22:21

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This pull request removes a simulator-driven motion-planning test that previously exercised random multi-robot movement and collision avoidance behavior.

Changes:

  • Deleted random_movement_test.py, which ran a multi-robot random-target navigation scenario and asserted no collisions plus target completion.
Comments suppressed due to low confidence (1)

utama_core/tests/motion_planning/random_movement_test.py:1

  • This PR deletes the only test that exercises RandomMovementStrategy (and its collision-avoidance behavior under repeated random target selection). After this change, the strategy remains in the codebase (e.g. utama_core/strategy/examples/motion_planning/random_movement_strategy.py and main.py) but has no test coverage, so regressions in random-target generation / callback invocation / multi-robot separation won’t be caught by CI.

If this test was removed due to flakiness or runtime, consider keeping it but marking it as an integration/slow test (so it’s opt-in), or replacing it with a smaller deterministic unit test for the strategy’s target selection + on_target_reached callback behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants