"Write tests" is easy advice. *What* to test at *which level* is the actual hard question.
## What it should cover
- A practical testing strategy for a typical product frontend (not a library)
- What belongs in unit tests, what's better as an integration test (e.g. Testing Library), what justifies E2E (Playwright/Cypress)
- Tests that look valuable but aren't (snapshot-everything, testing implementation details)
- Cost of each layer: speed, flakiness, maintenance
## Where it goes
`testing/what-to-test-where.md`
Strong opinions welcome, just explain the tradeoffs.
