Integration test: repository + widget data flow
epic-bufdir-report-period-selection-foundation-task-010 — Write an integration test that exercises the full data path from Supabase through both repositories into the PeriodPresetList and CustomDateRangePicker widgets. Use a Supabase test project with seeded data for a test organisation. Verify that presets load and render correctly, offline cache returns stale data when network is unavailable, and date range selection produces correct inputs for downstream aggregation queries.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 4 - 323 tasks
Can start after Tier 3 completes
Implementation Notes
Use a dedicated Supabase test project (separate from staging/prod) to avoid polluting real data. Store seeding and teardown SQL in a test/fixtures/ directory committed to the repo. For offline simulation, override the Supabase HTTP client with an interceptor that returns a network error after the first successful load — this validates the cache layer without requiring device network toggling. Use ProviderContainer overrides to inject the test-project Supabase client into repositories.
Assert repository query parameters by capturing calls via a spy wrapper around BufdirAggregationRepository rather than only asserting UI output — this makes the test more precise. Ensure the integration test file is under integration_test/ (not test/) so it is excluded from unit test runs and only executed explicitly.
Testing Requirements
Integration tests using flutter_test with a real Supabase test project (not mocked). Seed the test database with a known organisation ID, 3 preset configurations, and 10 activity records within a specific date range before running tests. Use a teardown hook to delete seeded data after each test run. Test scenarios: (1) online happy path — presets load and render, (2) offline fallback — disable network, assert stale cache renders, (3) date range selection triggers correct repository query parameters, (4) empty range edge case.
Run via flutter test integration_test/ in CI with Supabase credentials injected as env vars.
Supabase RLS policies for period preset configuration may be missing or incorrectly scoped, causing one organisation's presets to leak to another or write operations to fail silently.
Mitigation & Contingency
Mitigation: Define and review RLS policies for the bufdir_period_presets table in the migration file before any repository code is written. Include an integration test that verifies cross-organisation isolation using two distinct org credentials.
Contingency: If RLS is misconfigured in production, immediately disable the period preset fetch endpoint and fall back to hardcoded global presets until the policy is corrected and redeployed.
The activities table may lack a composite index on (organisation_id, activity_date), causing the range count query in BufdirAggregationRepository to perform a full table scan and exceed acceptable response time for large organisations.
Mitigation & Contingency
Mitigation: Add a migration that creates a composite index on (organisation_id, activity_date) as part of this epic. Benchmark the count query against a representative dataset (10 000+ rows) before marking the epic complete.
Contingency: If query latency is unacceptable after indexing, move the count query to a Supabase RPC function that leverages a materialised view or partial index, accepting a slight staleness window.
Flutter's native date picker widgets have known accessibility gaps (missing semantic labels, non-standard focus traversal) that may prevent WCAG 2.2 AA compliance out of the box, requiring a custom implementation.
Mitigation & Contingency
Mitigation: Evaluate third-party accessible date picker packages (e.g., table_calendar with custom semantics) against WCAG 2.2 AA criteria before beginning implementation. Document the chosen approach in the epic kick-off.
Contingency: If no package meets accessibility requirements, implement a simple text-field-based date entry with explicit semantic labels and format hints as an accessible fallback, deferring a fully visual calendar to a later iteration.