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>
- Fix DeviceIdentification tests by properly seeding device cache in test environment
- Fix integration tests by simplifying CSS selectors and removing invalid mock stubs
- Add proper aliases for Devices and Repo modules in device identification tests
- Improve database connection handling in Wallaby integration tests
- Add newline to end of tracked_callsign_old_packet_test.exs
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Address browser testing reliability in CI environments:
## CI/CD Improvements
- **ChromeDriver**: Use latest stable version instead of pinned version for better compatibility
- **Timeouts**: Add 10-minute timeout for integration tests to prevent CI hangs
- **Environment Variables**: Configure WALLABY_MAX_WAIT_TIME for CI-specific timeouts
## Wallaby Configuration Enhancements
- **Chrome Args**: Add CI-stable Chrome options (--no-sandbox, --disable-dev-shm-usage)
- **Window Size**: Set consistent 1280x720 window size for reproducible tests
- **Dynamic Timeouts**: Environment-configurable max wait time with sensible defaults
- **Pool Size**: Limit to single browser instance to prevent resource conflicts
## Benefits
- ✅ More reliable test execution in CI environments
- ✅ Better error handling and timeout management
- ✅ Consistent browser behavior across environments
- ✅ Reduced flakiness from resource constraints
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
This commit implements browser-based integration testing for the Phoenix LiveView
application using Wallaby and ChromeDriver to test the complete user experience
including JavaScript interactions.
## Changes Made
### Testing Infrastructure
- Add Wallaby dependency for browser automation testing
- Configure Chrome driver with headless mode for CI/CD
- Set up Phoenix server integration for test environment
- Enable screenshot capture on test failures
### Integration Tests
- `test/integration/simple_integration_test.exs` - Basic homepage functionality
- `test/integration/map_integration_test.exs` - Map interface and routing tests
- Tests validate page loading, content rendering, and navigation
### CI/CD Integration
- Update GitHub Actions workflow to install ChromeDriver
- Add separate integration test step in CI pipeline
- Configure headless Chrome for automated testing
### Configuration Updates
- Enable Phoenix server in test environment for Wallaby
- Configure Wallaby with proper base URL and screenshot settings
- Initialize Wallaby application in test helper
## Features Tested
- ✅ Homepage loads with APRS content
- ✅ Main page structure renders correctly
- ✅ Route navigation functions properly
- ✅ Basic Phoenix LiveView functionality
## Next Steps
This provides a solid foundation for expanding to test:
- Interactive map controls and JavaScript functionality
- Real-time packet updates via LiveView PubSub
- User authentication flows and form submissions
- Mobile responsive behavior
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
