From 1b2f6c6b214430ef7c61b0c10a0d15082a7774b5 Mon Sep 17 00:00:00 2001 From: Nora Date: Thu, 2 Jul 2026 17:18:16 -0600 Subject: [PATCH] test(sp32): bump migration version assertions to 19 --- backend/tests/test_acks.py | 9 +++++---- backend/tests/test_db_migrate.py | 8 +++++--- 2 files changed, 10 insertions(+), 7 deletions(-) diff --git a/backend/tests/test_acks.py b/backend/tests/test_acks.py index 3d1d560..cb11a88 100644 --- a/backend/tests/test_acks.py +++ b/backend/tests/test_acks.py @@ -51,7 +51,7 @@ def test_migration_0002_creates_acks_table(): def test_migration_latest_idempotent_on_fresh_db(): """Re-running the migration on the same DB must be a no-op (PRAGMA - user_version already at the latest version — currently 18 after + user_version already at the latest version — currently 19 after 0004-0006 line_reconciliation, 0005 ta1_acks, SP9's 0007 providers/payers/clearhouse, SP10's 0008 payer_rejected, SP11's 0009 audit_log, SP14's 0010 payer_rejected_acknowledged, @@ -60,15 +60,16 @@ def test_migration_latest_idempotent_on_fresh_db(): SP22's 0015 drop_claims_unique_constraint, SP27-Task 11's 0016 claims.matched_remittance_id index, SP27-Task 17's 0017 claim.patient_control_number backfill UPDATE, SP28's 0018 - claim_acks join table).""" + claim_acks join table, SP32's 0019 + rendering_provider_npi + service_provider_npi).""" with db.engine().begin() as c: v1 = c.exec_driver_sql("PRAGMA user_version").scalar() or 0 - assert v1 == 18 + assert v1 == 19 # A second run should not raise and should not bump the version. db_migrate.run(db.engine()) with db.engine().begin() as c: v2 = c.exec_driver_sql("PRAGMA user_version").scalar() or 0 - assert v2 == 18 + assert v2 == 19 def test_add_ack_persists_row(): diff --git a/backend/tests/test_db_migrate.py b/backend/tests/test_db_migrate.py index 995b0be..add5174 100644 --- a/backend/tests/test_db_migrate.py +++ b/backend/tests/test_db_migrate.py @@ -124,14 +124,16 @@ def test_migration_latest_idempotent_on_fresh_db(tmp_path: Path) -> None: SP27 Task 17 bumped it to 17 with the patient_control_number backfill UPDATE (the migration runner now applies DML too). SP28 bumped it to 18 with the claim_acks join table. + SP32 bumped it to 19 with rendering_provider_npi + + service_provider_npi on claims and remittances. """ engine = _fresh_engine(tmp_path) db_migrate.run(engine) v_after_first = _user_version(engine) - assert v_after_first == 18, f"expected head=18, got {v_after_first}" + assert v_after_first == 19, f"expected head=19, got {v_after_first}" db_migrate.run(engine) - assert _user_version(engine) == 18, "second run should not bump version" + assert _user_version(engine) == 19, "second run should not bump version" def test_drop_claims_unique_constraint_migration(tmp_path: Path, monkeypatch: pytest.MonkeyPatch) -> None: @@ -157,7 +159,7 @@ def test_drop_claims_unique_constraint_migration(tmp_path: Path, monkeypatch: py engine = _fresh_engine(tmp_path) db_migrate.run(engine) - assert _user_version(engine) == 18, f"expected head=18, got {_user_version(engine)}" + assert _user_version(engine) == 19, f"expected head=19, got {_user_version(engine)}" # Two claims in one batch with the same patient_control_number # must be insertable. If 0015's table recreation re-introduced a