Integration test SummaryShareService platform flows
epic-annual-impact-summary-core-services-task-016 — Write integration tests for SummaryShareService covering: screenshot capture produces non-null Uint8List output, iOS permission grant path routes to gallery save, iOS permission denied path presents settings dialog, Android share sheet is invoked with correct file MIME type, clipboard path copies image bytes and shows confirmation toast, and ShareResult reflects correct success/failure status. Use flutter_test integration test runner with platform channel mocks for permission APIs.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 5 - 253 tasks
Can start after Tier 4 completes
Implementation Notes
Platform channel names must match exactly what the underlying plugins use (e.g., 'plugins.flutter.io/image_gallery_saver', 'flutter/clipboard'). Discover these by reading the plugin source or running with verbose channel logging. For the iOS permission flow, mock the permission_handler plugin channel, not a custom channel. Use pumpAndSettle() after share() calls to allow async state propagation before asserting widget tree.
To test the settings dialog, assert find.byType(AlertDialog) and optionally find.text('Open Settings'). Avoid testing on a real device in CI — the integration_test package supports headless execution when platform channels are fully mocked.
Testing Requirements
Integration tests using flutter_test integration_test package with WidgetTester for UI assertions and TestDefaultBinaryMessengerBinding.instance.setMockMethodCallHandler for platform channel mocking. Each platform flow is a separate testWidgets() block. Use setUp() and tearDown() to register/restore channel mocks. Assert both the return value (ShareResult) and side effects (widget tree changes, channel invocations).
For channel invocation verification, capture calls in a local list within the mock handler and assert list length and argument values after the share() call completes.
Activity records may contain duplicate entries (as evidenced by the duplicate-detection feature dependency) or proxy-registered activities that should be attributed differently. Including duplicates or mis-attributed records would produce inflated stats, undermining trust in the summary.
Mitigation & Contingency
Mitigation: Implement the aggregation query to join against the deduplication-reviewed-flag on activity records and filter out unresolved duplicates. Coordinate with the duplicate-detection feature team to confirm the authoritative flag field before implementing the RPC. Include a data-quality warning in the summary when unresolved duplicates are detected.
Contingency: If deduplication state is unreliable at release time, add a prominent disclaimer in the summary UI noting that figures reflect all registered activities and may include duplicates pending review. Track a follow-up task to re-aggregate after deduplication runs.
Each organisation wants to define their own milestone thresholds (e.g., NHF's counting model differs from HLF's certification model). Implementing configurable thresholds may expand scope significantly if the configuration UI is expected in this epic.
Mitigation & Contingency
Mitigation: Scope this epic strictly to the evaluation engine and a hardcoded default threshold set. Define the MilestoneDefinition interface with an organisation_id discriminator so per-org configs can be loaded from the database in a later sprint. Build the admin configuration UI as a separate follow-on task outside this epic.
Contingency: If stakeholders require per-org milestone configuration before launch, deliver a JSON-based configuration file per org as an interim solution, loaded from Supabase storage, until a full admin UI is built.
Android 13+ restricts access to media collections and requires READ_MEDIA_IMAGES permission for gallery saves, while older Android versions use WRITE_EXTERNAL_STORAGE. Handling both permission models correctly across the device matrix is error-prone.
Mitigation & Contingency
Mitigation: Use the permission_handler Flutter package with version-aware permission requests abstracted behind the summary-share-service interface. Write platform-specific unit tests for both Android API levels in the test harness. Test on a minimum of three Android versions (API 29, 32, 34) in CI.
Contingency: If gallery save is broken on specific Android versions at launch, disable the 'Save to gallery' option on affected API levels and surface only clipboard and system share sheet, which require no media permissions.