Widget integration tests and golden tests
epic-periodic-summaries-ui-task-012 — Write integration and golden tests for all three widgets. Integration tests must cover: card dismissal persists state, pull-to-refresh triggers BLoC reload, outlier filter toggle updates list, tap-through navigation routes correctly, and comparison widget handles zero prior-period values. Golden tests must capture approved renders for both light and dark themes at multiple screen sizes. Tests must run in CI on each commit.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 7 - 84 tasks
Can start after Tier 6 completes
Implementation Notes
Organize test files to mirror the source structure: test/widgets/coordinator_team_summary_view_test.dart, test/widgets/periodic_summary_card_test.dart, test/widgets/period_comparison_widget_test.dart. Create a shared test/fixtures/mentor_summary_fixtures.dart file with factory functions that generate fake MentorSummaryModel instances — this prevents duplication across test files. For golden tests, run flutter test --update-goldens locally to generate the initial approved baseline files, then commit them. Add a CI step that runs flutter test without --update-goldens and fails if any golden differs.
For the BLoC integration tests, define a simple FakeBloc that implements the Stream
Testing Requirements
All tests use flutter_test. Use FakeCoordinatorTeamSummaryBloc (manually crafted fake implementing Bloc interface) to emit predefined state sequences. For golden tests, use flutter_test's matchesGoldenFile and commit approved goldens to test/goldens/. Set window size per test using tester.binding.window.physicalSizeTestValue and tester.binding.window.devicePixelRatioTestValue.
Use NavigatorObserver mock (or GoRouter's testing utilities) to verify navigation calls without running a real navigator. Cover both ThemeData.light() and ThemeData.dark() in all golden tests by wrapping the widget under test in a MaterialApp with the respective theme. Integration tests use pumpWidget + pumpAndSettle; avoid real timers.
If the cached summary is from a prior period (e.g., previous quarter's card is still cached), the digest card could appear on the home screen with outdated numbers after a new period begins, confusing users who have already seen that data.
Mitigation & Contingency
Mitigation: In the SummaryCacheRepository, store the period_start and period_end alongside cached data. In the PeriodicSummaryCard BLoC, compare the cached record's period against the current date using PeriodCalculatorService. Only render the card if the cached summary belongs to the active period.
Contingency: If stale cards appear in production, push a hotfix that adds the period validity check to the BLoC and clears all cached summaries older than the current period boundary via a forced cache flush on next app launch.
Using colour alone to distinguish underactive from overloaded mentors in the coordinator view would fail WCAG 1.4.1 (use of colour). This is especially critical for organisations serving users with colour vision deficiency.
Mitigation & Contingency
Mitigation: Always pair colour indicators with a text label or icon (e.g., a downward arrow + 'Underactive' text alongside the amber colour). Use the contrast-safe-color-palette design tokens throughout. Run the contrast-ratio-validator on all new colour combinations in CI.
Contingency: If an accessibility audit flags colour-only indicators post-launch, introduce icon-based indicators as a patch release and update the design token definitions to enforce the paired-indicator pattern going forward.
Inserting a new card into the role-based home screen requires changes to shared home screen widget composition, which may conflict with parallel feature branches also modifying the home screen layout, causing merge conflicts and integration delays.
Mitigation & Contingency
Mitigation: Implement the PeriodicSummaryCard as a fully self-contained widget that the home screen conditionally renders based on a BLoC state flag. Minimise changes to the home screen itself to a single conditional insertion point, reducing the surface area for merge conflicts.
Contingency: If integration conflicts block the PR, isolate the card behind the organisation-scoped feature flag so it can be toggled independently and merged without affecting other home screen changes.