The integration tests were failing because the map was loading at a default
location that didn't include the test packets. The tests were creating
packets in specific locations but the map view wasn't centered on them.
Changes:
- Center first test on New York area (40.735, -73.996) where test packets are
- Center other tests on central US (39.8283, -98.5795) for broader view
- Add appropriate zoom levels for each test scenario
- Ensure all test URLs include location parameters
This ensures the test packets are within the map viewport when the tests
run, allowing the markers to be visible and clickable.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
The Wallaby integration tests were timing out in CI. This adds proper
configuration for running browser tests in the CI environment.
Changes:
- Start ChromeDriver explicitly in the background on port 4444
- Pass CHROMEDRIVER_URL environment variable to tests
- Add chromedriver_base_url configuration to use env var if available
- Increase test timeout to 60 seconds for integration tests
- Add additional Chrome flags for better CI stability:
- --disable-setuid-sandbox
- --disable-extensions
- --disable-background-timer-throttling
- --disable-backgrounding-occluded-windows
- --disable-renderer-backgrounding
These changes ensure ChromeDriver is properly started and accessible
in the CI environment, preventing connection timeouts.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
The integration tests were failing in CI with DBConnection.OwnershipError
because they were missing the required Ecto.Adapters.SQL.Sandbox setup.
Changes:
- Added proper sandbox checkout and shared mode configuration
- Fixed incorrect CSS selector (#map -> #aprs-map)
- Configured tests to use real Packets module instead of mocks
- Ensured database connections are properly managed in Wallaby tests
This matches the setup pattern used in other integration tests and
resolves the CI failures.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Fix time-dependent tests to use relative dates instead of hardcoded values
- Increase timeout values to prevent flaky failures on slower systems/CI
- Use flexible string matching for time-related assertions
- Update Process.sleep and assert_receive timeouts for better reliability
Specific changes:
- TimeHelpers: Use pattern matching for variable time strings
- PacketsOldest: Replace hardcoded dates with relative calculations
- BroadcastTaskSupervisor: Increase timing assertion to 1s
- Movement tests: Increase refute_push_event timeout to 2s
- Integration tests: Increase all wait times by 50%
- StreamingPacketsPubSub: Increase receive timeouts
These changes ensure tests pass regardless of when they're executed
and are more resilient to performance variations in CI environments.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Enhanced LiveView tests to verify historical loading behavior
- Added tests for valid/invalid bounds handling
- Added tests for zoom-based packet limits
- Created integration tests for full browser-based historical loading verification
- Tests ensure packets are loaded immediately when map initializes
- Tests verify different historical time ranges work correctly
- Tests confirm tracked callsigns load all packets regardless of bounds
These tests ensure the historical packet loading feature works reliably across different scenarios.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
