Widget tests for affiliation chip and status indicator
epic-contact-detail-and-edit-foundation-task-015 — Write Flutter widget tests for multi-chapter-affiliation-chip (read-only render, edit mode selection, 5-chapter cap enforcement, empty state) and assignment-status-indicator (all three status colours, org label override, screen reader semantics). Use flutter_test and verify golden snapshots for critical states.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 4 - 323 tasks
Can start after Tier 3 completes
Implementation Notes
Create a shared `test_helpers.dart` in `test/widgets/contact/` that builds a minimal MaterialApp wrapper with design token theme applied — do not repeat this boilerplate in every test file. Use a `FakeChapterRepository` stub (simple in-memory list) rather than mocking Supabase — these are pure widget tests and must not hit the network. For the cap enforcement test, build the widget with `selectedIds` already containing 5 items and assert `IgnorePointer` is active using `tester.widget
Golden snapshot CI setup: ensure `--dart-define=FLUTTER_TEST_GOLDENS=true` flag is used in CI to skip golden updates and only verify. Document how to update goldens locally in a comment block at the top of each golden test file.
Testing Requirements
This task IS the testing task. Use `flutter_test` exclusively — no third-party test libraries. Structure tests with clearly named `group()` blocks per widget and `testWidgets()` per scenario. Use `find.byType`, `find.text`, and `find.byKey` for locating widgets.
Prefer `pump()` over `pumpAndSettle()` for synchronous widget operations. For golden tests, use `matchesGoldenFile` and store snapshots in `test/goldens/`. Run `flutter test --update-goldens` only when intentionally updating; goldens must be committed and reviewed in PRs. Accessibility tests should use `tester.getSemantics()` to assert meaningful `SemanticsNode` labels.
Blindeforbundet's encryption key retrieval mechanism may not be finalised at implementation time, or session key availability via Supabase RLS may be inconsistent, causing decryption failures that expose masked placeholders to users and degrade the experience.
Mitigation & Contingency
Mitigation: Agree with Blindeforbundet on key storage and retrieval contract before implementation starts. Prototype key retrieval in a spike against the staging Supabase instance and validate the full decrypt/verify cycle with real test data before committing to the implementation.
Contingency: Implement a fallback that shows a 'field temporarily unavailable' state with a retry affordance. Log decryption failures server-side for audit. Escalate to Blindeforbundet stakeholders to unblock key management before the service tier epic begins.
NHF contacts may belong to up to 5 chapters, each governed by separate RLS policies. A coordinator's chapter scope may not cover all affiliations, causing partial profile reads or silent data omissions that are difficult to detect in tests.
Mitigation & Contingency
Mitigation: Map all RLS policy combinations for multi-chapter contacts early. Write integration tests that create contacts with 5 affiliations and query them from coordinators with varying chapter scopes. Use Supabase's RLS test utilities to verify row visibility per role.
Contingency: Add an explicit 'affiliation partially visible' state in the repository response model so the UI can communicate scope limitations to the coordinator rather than silently showing incomplete data.
Organisation-specific validation rules (e.g., NHF chapter limit, Blindeforbundet encrypted field edit flow) may expand in scope during implementation as edge cases are discovered, causing the validator to grow beyond the planned complexity.
Mitigation & Contingency
Mitigation: Define the complete validation rule set with product and org stakeholders before coding begins. Document each rule with its source organisation and acceptance test. Use a rule registry pattern so new rules can be added without modifying core validator logic.
Contingency: Timebox validator enhancements to 2 hours per additional rule. Defer non-blocking rules to a follow-on maintenance task rather than blocking the epic delivery.