ContractTests
Verifying two services agree on an API contract without a full E2E test — catches breaking changes early.
Why we need this / what value this brings
Catches an API-breaking change the moment it's introduced, without needing a full, slow e2e test to notice.
When to use this
Once there are two independently-deployed services that need to agree on an API shape.
How to use or implement this
Not yet needed for a single backend + single frontend — revisit if/when services split.
Research questions
- Would this matter yet for Localz (single backend, single frontend) or only once services split?
Empty folder — drop notes, links, and findings here as you research.