test(pipelines): forward dry_run_override in offline test PapraConfig fixtures #96
Reference in New Issue
Block a user
Delete Branch "backend-engineer/fix-dry-run-override-tests"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Story #93 Traces to: Epic — INB-331 (CEO-routed dispatch). API contract ref: N/A (build-defect fix, no API surface change). Schema ref (Pattern A): N/A (no data model change). Endpoints: N/A. Migrations: N/A. Security review (Pattern D): N/A. What is broken
PapraConfig.__init__gained a new keyword-only parameterdry_run_override(commit980cc19vicinity). Two offline test fixtures inpipelines/_tests/constructPapraConfig(...)without forwarding this parameter, causingTypeErroron every branch descending frommain: -test_live_pipeline_offline.py: 4 of 14 tests fail. -test_historical_pipeline_offline.py: same signature mismatch (blocked by same regression). Fix Adddry_run_override=dry_runto_make_papra_cfg(...)in both files. This maps the existing test-leveldry_runflag into the new parameter, preserving fixture semantics. Verification -python3 pipelines/_tests/test_live_pipeline_offline.py→ 14/14 passed. - Searchedgrep -rn "PapraConfig(" pipelines/_tests/— all other callsites already includedry_run_override. Test plan: CIFast offline testsjob should go green on this PR. Reviewer: @cto