Write Widget Tests for Driver UI Components
epic-driver-and-confidentiality-management-ui-task-014 — Write Flutter widget tests for all driver UI components: DriverFeatureFlagGuard (enabled/disabled flag states), DeclarationStatusBadge (all status variants), DriverAssignmentList (empty, loading, populated, error states with pagination), DeclarationSendScreen (send and re-send flows), DeclarationAcknowledgementScreen (scroll gate, checkbox enable/disable, submission), and DriverFeeRegistrationForm (validation paths and declaration-required state). Target 80%+ widget test coverage for this epic.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 5 - 253 tasks
Can start after Tier 4 completes
Implementation Notes
Organize tests into one file per component rather than one large file, to keep test files maintainable and parallelizable on CI. Use setUp() to create fresh BLoC/provider instances before each test — never share mutable BLoC state between tests. For the scroll gate test, the real scroll detection likely uses a ScrollController with a listener; in tests, use tester.drag(find.byType(SingleChildScrollView), const Offset(0, -500)) to simulate scrolling to the bottom, then pump() to let listeners fire. For BLoC-driven tests, always use bloc_test's blocTest() to assert state sequences rather than manually pumping events and asserting state — this is less brittle.
When testing the DriverFeatureFlagGuard flag-change mid-session test, use a StreamController
Testing Requirements
All tests are Flutter widget tests using flutter_test. Use bloc_test's blocTest() helper for BLoC unit tests. Use Riverpod's ProviderContainer with overrides for provider tests. Use mocktail for service stubbing (preferred over mockito for null-safety compatibility).
Each widget test pumps the widget under test inside a MaterialApp with the app's theme and design tokens applied so visual assertions are meaningful. Pagination tests use a FakeScrollController to simulate scroll events. The scroll gate test on DeclarationAcknowledgementScreen uses tester.drag() to simulate scroll progress. Snapshot/golden tests are out of scope for this task.
The declaration acknowledgement screen has the most complex accessibility requirements of any screen in this feature: scrollable long-form legal text, a conditional checkbox that is only enabled after reading, and a timestamp capture. Incorrect focus management or missing semantics annotations could fail VoiceOver navigation or cause the screen reader to announce the checkbox as available before the driver has scrolled, undermining the legal validity of the acknowledgement.
Mitigation & Contingency
Mitigation: Build the acknowledgement screen against the WCAG 2.2 AA checklist from the start, not as a post-hoc audit. Use semantics-wrapper-widget and live-region-announcer from the platform's accessibility toolkit. Include a VoiceOver test session in the acceptance criteria with a tester using the screen reader.
Contingency: If WCAG compliance cannot be fully achieved within the sprint, ship the screen with a documented list of accessibility gaps and a follow-up sprint commitment. Do not block the declaration workflow launch if the core interaction works but a non-critical semantics annotation is missing.
Drivers receive a push notification with a deep link to the declaration acknowledgement screen for a specific assignment. If the deep link handler does not correctly route to the right screen and assignment context — particularly when the app is launched cold from the notification — the driver may see a blank screen or the wrong declaration.
Mitigation & Contingency
Mitigation: Implement and test all three notification scenarios: app foregrounded, app backgrounded, and cold start. Use the platform's existing deep-link-handler infrastructure. Add integration tests that simulate notification tap events and assert correct screen and data loading.
Contingency: If cold-start deep link routing proves unreliable, implement a notification-centre fallback where the driver can find the pending declaration from the notification centre screen, ensuring the workflow can always complete even if the direct deep link fails.
If the driver-feature-flag-guard has any rendering edge case — such as a brief flash of driver UI before the flag value is loaded, or a guard that fails open on a flag service error — driver-specific UI elements could be momentarily visible to coordinators in organizations that have not opted in, causing confusion and potentially a support escalation.
Mitigation & Contingency
Mitigation: Default the guard to rendering nothing (not a loading indicator) until the flag value is definitively resolved. Treat flag service errors as flag-disabled to fail closed. Write widget tests covering the loading, disabled, and enabled states including the error case.
Contingency: If fail-closed cannot be guaranteed within the sprint, add a server-side RLS check on the driver assignment endpoints so that even if the UI guard leaks, the data layer refuses to return driver data for organizations without the flag enabled.