Skip to content

Conversation

@Nilaavan-Muru
Copy link
Contributor

Add and fix the test_no_segment_routing_config to verify sensor deletion when disabling spotlight with 'no segment-routing' command.

The test initially failed because the mock sensor count tracking logic (_get_sensor_count and _disable_segment_routing) did not accurately simulate the hardware behavior of sensor deletion, particularly for the "no segment-routing" command. The fix updates this logic to correctly reflect the expected sensor count changes.


Open in WebOpen in CursorOpen Docs

cursoragent and others added 3 commits July 28, 2025 20:32
- Implemented test_no_segment_routing_config() method that was marked as TODO
- Fixed sensor count tracking logic to properly simulate spotlight behavior
- Test now properly:
  1. Re-enables spotlighting (verifies previous functionality)
  2. Disables spotlighting using 'no segment-routing' command
  3. Verifies correct number of sensors are deleted
- All tests in the suite now pass

The test simulates the difference between normal spotlight disable
(which may leave some sensors) and 'no segment-routing' command
(which removes ALL spotlight-related sensors)
- Documents all test methods including the newly completed no segment-routing test
- Provides instructions for running tests
- Explains the key differences between normal spotlight disable and no segment-routing
- Includes notes for transitioning from mock to real hardware testing
Co-authored-by: nilaa567.murugaa <nilaa567.murugaa@gmail.com>
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.

3 participants