Testing

The G2P Bridge is tested at several complementary layers:

Layer	Scope	Where
Unit Testing	White-box, mocked services/DB — fast, run in CI on every commit	core/**/tests/
Regression Sanity Suite	Black-box, point-at-a-deployed-system — every API + full end-to-end cash flow verified stage by stage, plus business-rule negatives and MT940 reconciliation errors	test/sanity/
API Walkthrough (Postman)	Manual, learn-by-doing run through the disbursement APIs with editable CSV seed data — same flow as the sanity suite, but you drive it; doubles as training	test/api-walkthrough/
Performance Testing	Load / throughput	test/

Use the unit tests to catch code-logic regressions, the regression sanity suite to confirm an installed environment works end to end (it now also covers the API-level negative scenarios and MT940 reconciliation-error checks that were previously standalone Postman/script artefacts), the API Walkthrough for a hands-on/training run against an installed system, and performance testing for scale.