Integration testing for form engine pipeline
epic-structured-post-session-report-form-engine-task-013 — Write integration tests covering the full form engine pipeline: schema load → field rendering → user input → validation → draft save → submission. Use flutter_test with mock Supabase client. Test scenarios: required field validation blocks submission, speech-to-text transcription fills field, way-forward item add/edit/remove, draft auto-save triggers on field change, successful submission clears draft, and schema with all field types renders without errors. Target 90% branch coverage on orchestrator and validator.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 4 - 323 tasks
Can start after Tier 3 completes
Implementation Notes
For the full pipeline integration tests, instantiate the real FormOrchestratorBloc with mock repositories injected via constructor. Use BlocProvider.value in the widget test to supply it to the widget tree. For debounce testing, wrap in fakeAsync and use fake.elapse(Duration(seconds: 2)) — do not use real.delay(). For the SpeechToText scenario, mock the SpeechToTextService to synchronously return a transcription string and verify the field value updates.
Organize test files to mirror source files: test/orchestration/form_orchestrator_bloc_test.dart, test/visualization/dynamic_field_renderer_test.dart, test/visualization/way_forward_section_widget_test.dart, test/integration/form_engine_pipeline_test.dart. Use descriptive test names in the format 'given [state], when [event], then [outcome]' for readability in CI output.
Testing Requirements
This task IS the testing work. Organize tests into test groups: (1) OrchestratorBloc unit tests (bloc_test), (2) DynamicFieldRenderer widget tests, (3) WayForwardSectionWidget widget tests, (4) full pipeline integration tests using pumpWidget with real bloc wired to mock repositories. Use testWidgets for full pipeline tests. Use fakeAsync for all debounce/timer tests.
Set up a shared test fixtures file with a complete mock schema containing all 8 field types and sample options. Generate coverage report with 'flutter test --coverage' and enforce ≥90% branch coverage for orchestrator and validator in CI via lcov threshold check.
Dynamically rendered form fields built from runtime JSON schema are significantly harder to make accessible than statically declared widgets — Flutter's Semantics tree must be correct for every possible field type and every validation state. Failures here block the entire feature for Blindeforbundet's visually impaired peer mentors.
Mitigation & Contingency
Mitigation: Define WCAG 2.2 AA semantics requirements for each field type before implementation and write widget tests using Flutter's SemanticsController for every type. Include a real-device VoiceOver test session in the acceptance gate for this epic before marking it done.
Contingency: If dynamic semantics prove too difficult to get right generically, implement field-type-specific Semantics wrappers (one per supported field type) instead of a single generic renderer, accepting slightly more code duplication in exchange for reliable accessibility.
The report-form-orchestrator must manage a complex state machine — schema loading, draft persistence, per-field validation, submission retries, and error recovery — across multiple async operations. Incorrect state transitions could result in lost user data, double submissions, or UI freezes.
Mitigation & Contingency
Mitigation: Define all Bloc states and events explicitly as sealed classes before writing any logic. Use a state machine diagram reviewed by the team before implementation. Write exhaustive Bloc unit tests covering every state transition, including concurrent events and network interruption mid-submission.
Contingency: If Bloc complexity becomes unmanageable, extract draft persistence into a separate DraftManagerCubit and keep report-form-orchestrator focused solely on the submit workflow. The additional granularity makes each component independently testable.
Organisations may require field types beyond the five currently specified (text, multiline, checkbox group, radio, date). If a new type is discovered during pilot testing, the dynamic-field-renderer must be extended, potentially requiring changes across multiple layers.
Mitigation & Contingency
Mitigation: Design dynamic-field-renderer as a registry of field-type renderers with a clear extension point. Document the pattern for adding a new field type so that it can be done in one file without touching existing renderers.
Contingency: If an unhandled field type is encountered at runtime, dynamic-field-renderer renders a labelled plain-text fallback widget and logs a warning so the missing type is surfaced in monitoring, preventing a crash while making the gap visible.