Testing
Test strategy across the pyramid — see SYSTEM_DESIGN_ALIGNMENT.md section 9.5 for the full breakdown (unit through mutation testing).
Why we need this / what value this brings
Tests are what let you change code with confidence instead of fear — the ROI compounds as the codebase grows.
When to use this
Write tests alongside the code, not after — retrofitting tests onto untested code is far more work and usually gets skipped.
How to use or implement this
Prioritize tests around the highest-stakes, highest-change-frequency code first (the booking/payment flow), not 100% coverage everywhere equally.
Subtopics
Research questions
- What's Localz's actual test coverage today across backend/ and frontend/ — is there a stated test pyramid target?
Empty folder — drop notes, links, and findings here as you research.