Unit test CertificationRepository with mock Supabase client
epic-certification-management-foundation-task-011 — Write comprehensive unit tests for CertificationRepository: test all CRUD methods, expiry queries, and error paths using a mock Supabase client. Verify RLS context is passed correctly, JSONB renewal_history serialises and deserialises without loss, and expiry date boundary conditions are handled correctly (same-day expiry, midnight UTC).
Acceptance Criteria
Technical Requirements
Execution Context
Tier 4 - 323 tasks
Can start after Tier 3 completes
Implementation Notes
Use `mocktail` (preferred over Mockito for Dart null-safety ergonomics) to create `MockSupabaseClient`, `MockSupabaseQueryBuilder`, etc. The Supabase client has a deeply chained query builder API — you will need to mock the full chain (`.from().select().eq().gte().execute()`). Consider creating a `FakeSupabaseClient` test double that records calls and returns pre-configured fixtures, as this is often more readable than chaining mock expectations. For JSONB tests: construct a `List
For boundary date tests: use `DateTime.utc(2026, 3, 26, 0, 0, 0)` explicitly — never `DateTime.now()` in test assertions. Place tests in `test/repositories/certification_repository_test.dart`. Run with `flutter test test/repositories/certification_repository_test.dart --coverage`.
Testing Requirements
Unit tests only — no integration tests in this task. Use flutter_test with Mockito or mocktail to mock the Supabase client. Structure tests in groups: 'CertificationRepository.create', 'CertificationRepository.read', 'CertificationRepository.update', 'CertificationRepository.delete', 'CertificationRepository.expiry queries', 'CertificationRepository.JSONB serialisation', 'CertificationRepository.error handling'. Use `setUp()` to initialise fresh mocks before each test.
For date boundary tests, inject a fixed `DateTime` via a `ClockProvider` or similar abstraction — avoid `DateTime.now()` in repository implementation. Run `flutter test --coverage` and verify lcov report shows >= 90% line coverage on the repository file.
HLF Dynamics portal webhook API contract may be undocumented, subject to change, or require a separate authentication flow not yet agreed upon with HLF. If the contract changes post-implementation, the sync service silently fails and expired peer mentors remain on public listings.
Mitigation & Contingency
Mitigation: Obtain the official Dynamics webhook specification and test credentials from HLF before starting HLFDynamicsSyncService implementation. Agree on a versioned webhook contract and request a staging endpoint for integration testing.
Contingency: If the contract is unavailable, stub the sync service behind a feature flag and ship without Dynamics sync initially. Queue sync events locally and replay once the contract is confirmed.
Supabase RLS policies for certifications must correctly scope data to the coordinator's chapter without leaking cross-organisation data, particularly complex in multi-chapter membership scenarios. A misconfigured policy could expose peer mentor PII to wrong coordinators.
Mitigation & Contingency
Mitigation: Write RLS policies against the established org-hierarchy schema used by other tables. Peer review all policies before migration deployment. Add integration tests that assert cross-organisation data isolation using test accounts with different org scopes.
Contingency: If a policy gap is discovered post-merge, immediately disable the affected query endpoint and apply a hotfix migration. Audit access logs in Supabase for any cross-org data access events.
Storing renewal history as a JSONB field rather than a normalised table simplifies queries but makes retrospective schema changes (adding fields to history entries) harder and could cause issues if history grows very large for long-tenured mentors.
Mitigation & Contingency
Mitigation: Define a versioned JSONB entry schema (include a schema_version field in each entry) so future migrations can transform old entries. Add a size guard in the repository to warn if renewal_history exceeds 500 entries.
Contingency: If JSONB approach proves limiting, add a normalised certification_renewal_events table and migrate history entries in a background job, keeping the JSONB field as a read cache.