Write unit tests for PartialTranscriptionRepository
epic-speech-to-text-input-foundation-task-003 — Write comprehensive unit tests for all PartialTranscriptionRepository methods using an in-memory SQLite test database. Cover: successful save and retrieval, session-scoped isolation, stale record cleanup, concurrent write safety, and crash-recovery scenario where saved data survives app restart simulation.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 2 - 518 tasks
Can start after Tier 1 completes
Implementation Notes
Create a `test/fixtures/partial_transcription_fixture.dart` helper that returns a valid `PartialTranscription` with all fields populated. Parameterize `sessionId`, `createdAt`, and `persistenceStatus` to make scenario setup concise. For the stale test, construct records with `createdAt` set to `DateTime.now().subtract(Duration(days: 8))` and verify `clearStale(Duration(days: 7))` removes them. Do not use `mockito` or `mocktail` for the repository itself — test the real implementation against an in-memory DB for maximum fidelity.
If drift is used instead of sqflite, use drift's built-in `NativeDatabase.memory()` test setup.
Testing Requirements
All tests are unit tests (no widget tree, no Flutter engine required beyond flutter_test). Use a `PartialTranscriptionFixture` factory class to generate test instances with sensible defaults, overridable via named parameters. Group tests by method name using `group()`. Use `setUp`/`tearDown` for DB lifecycle.
For the concurrent test, use `Future.wait(List.generate(10, (_) => repo.save(fixture())))` and then assert `findBySessionId` returns 10 records. For crash-recovery, simulate by closing and reopening the database with the same in-memory key (sqflite_common_ffi supports named in-memory DBs that persist across open/close within the same process).
iOS 15 on-device speech recognition has a 1-minute session limit and requires network fallback for longer sessions. Peer mentor way-forward dictation may routinely exceed this limit, causing silent truncation of transcribed content without user feedback.
Mitigation & Contingency
Mitigation: Implement session-chunking logic in NativeSpeechApiBridge that automatically restarts recognition before the limit is reached, preserving continuity via partial concatenation. Document the iOS 15 vs iOS 16 on-device recognition behaviour difference in code comments.
Contingency: If chunking causes user-visible interruptions, surface a non-blocking informational banner on iOS 15 devices informing users that very long dictation sessions may need to be broken into segments, and use PartialTranscriptionRepository to persist each chunk immediately.
On iOS, speech recognition permission can only be requested once. If the user denies the permission, the app cannot re-request it. A poor first-impression permission flow will permanently disable dictation for those users, impacting the Blindeforbundet blind-user base who rely on dictation most.
Mitigation & Contingency
Mitigation: Design the NativeSpeechApiBridge permission flow to show a clear pre-permission rationale screen before the OS dialog. Implement a graceful degradation path that hides the microphone button and shows a settings deep-link when permission is permanently denied.
Contingency: If users have already denied permission before the rationale screen is added, provide a settings deep-link in DictationScopeGuard's denial message directing users to iOS Settings > Privacy > Speech Recognition to re-enable manually.
The approved field IDs and screen routes configuration in DictationScopeGuard may fall out of sync with the actual report form schema as new fields are added by org administrators, silently blocking dictation on legitimately approved fields.
Mitigation & Contingency
Mitigation: Source the approved field configuration from the same org-field-config-loader used by the report form, rather than a hardcoded list. Add a developer-time assertion that logs a warning when a dictation-eligible field type is rendered but not in the approved routes map.
Contingency: Provide a runtime override mechanism in the scope guard that coordinators or admins can use to temporarily whitelist a field ID while the config is updated, with an automatic expiry.