End-to-End Export Pipeline Integration Test

Structure the test file in three phases: (1) Seed phase — helper functions that insert test organisations, test users, and test approved claims using the Supabase admin client; (2) Execute phase — invoke the RunExportPipelineUseCase for each exporter type using a real (not mocked) pipeline with real guard and real repository connected to the local Supabase; (3) Assert phase — query the database directly to verify claim state, export run records, and payload content. The concurrency/idempotency test (re-triggering the same period) is the highest-value test in this suite — it validates the core business invariant of the entire epic. Use a TestSupabaseClient helper that wraps the Supabase client with automatic organisation-scoped JWTs for test users, so each database call in the assertion phase is authenticated as the correct test user. Avoid sharing state between test cases via class-level variables — use local variables in each test() block to keep tests independent and debuggable.

Integration test suite using flutter_test with a real local Supabase instance (supabase CLI). Tests organised in a single E2E test file: export_pipeline_e2e_test.dart. Test lifecycle: setUpAll seeds test organisations, users, and approved claims; each test case is independent and uses its own claim IDs; tearDownAll removes all seeded data. Use Supabase's admin client (service role) only in setup/teardown helpers, never in test assertions.

Test assertions query the database directly via the test client to verify state — do not rely solely on return values from the pipeline. Include a dedicated RLS test case that attempts a cross-org query with a scoped JWT and asserts zero results returned. Run this suite in CI with supabase start as a prerequisite step.