Graham McIntire 4ac70a52c1 fix: Ensure integration tests properly trigger historical packet loading ... The integration tests were failing because historical packets weren't loading automatically. The tests needed to properly trigger the bounds update event after the map initializes. Changes: - Add PostGIS location field to packet fixtures when lat/lon are provided - Execute JavaScript to manually trigger bounds update after map loads - This ensures the sendBoundsToServer function is called - Adjusted timing to wait for map initialization before triggering This should make the integration tests more reliable by ensuring historical packets are loaded after the map is ready. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>		2025-08-03 15:57:48 -05:00
..
aprsme	updates with parser updates	2025-08-03 09:19:31 -05:00
aprsme_web	updates with parser updates	2025-08-03 09:19:31 -05:00
assets/js	Improve type safety for getTrailId function	2025-07-21 08:36:38 -05:00
integration	fix: Ensure integration tests properly trigger historical packet loading	2025-08-03 15:57:48 -05:00
support	fix: Ensure integration tests properly trigger historical packet loading	2025-08-03 15:57:48 -05:00
types	refactor to use external parser	2025-06-24 14:22:09 -05:00
test_helper.exs	fix: Comprehensive packet processing and test optimization improvements	2025-08-01 17:50:07 -05:00
time_independence_fixes.md	test: Make tests time-independent and increase timeouts for reliability	2025-08-02 10:07:47 -05:00