Repository navigation
v1.1.2
Test-only follow-up to v1.1.1. Backend CI went red on the v1.1.1 merge because two money-flow tests still asserted the old 4-stage shape (Allocated → Released → Spent → Flagged) that was removed in v1.1.1 when the misleading "Released" stage was dropped.
🧪 Test assertions realigned with 3-stage waterfall
tests/test_money_flow.py::TestCountyMoneyFlow::test_returns_waterfalltests/test_money_flow.py::TestNationalMoneyFlow::test_returns_national_aggregate
Changes:
len(stages) == 4→len(stages) == 3- Stage order assertion: Allocated / Spent / Flagged (was Allocated / Released / Spent / Flagged)
- New gap assertion: Allocated → Spent = 3.5M (was a two-gap cascade through the Released stage)
- New top-level assertion:
committed_amount == 13.8M— confirms the number still flows on the response, just as a supplementary field rather than a waterfall stage - Added a docstring explaining why the shape changed, so a future refactor doesn't re-expand to 4 stages without reading the rationale first
Local run: pytest backend/tests/test_money_flow.py — 7/7 pass.
No product behavior changes — only test code was touched.
Full Changelog: v1.1.1...v1.1.2