UnitIntegrationE2E

The core pyramid: unit tests (single function), integration tests (component + real dependency), e2e (full user journey).

Why we need this / what value this brings

Each level catches a different class of bug — unit tests catch logic errors cheaply, e2e tests catch integration issues that only show up end-to-end.

When to use this

Unit tests for pure logic; integration tests at component/DB boundaries; e2e for the critical user journeys that must never break.

How to use or implement this

Favor a pyramid shape (many unit tests, fewer integration, fewest e2e) — e2e tests are valuable but slow and brittle, so use them sparingly and deliberately.

Research questions

• Playwright is the E2E tool of choice per this project — but Clerk's Google-OAuth-only dev instance blocks synthetic login (see LocalzProblems/). How is that being worked around?

---

Empty folder — drop notes, links, and findings here as you research.