End-to-End Testing

Use Playwright to prove that a real user journey works across the boundaries most likely to fail together. Keep the suite small enough to trust and fast enough to run where failures still influence development.

1. Name the journey and risk

State the behavior in user language before writing browser steps:

Journey: <who does what and reaches which observable outcome>
Risk: <integration or regression this browser test can expose>
Boundaries: <browser, API, auth, database, queue, third party>
Existing coverage: <what unit or integration tests already prove>

Choose end-to-end coverage when the risk lives in wiring, browser behavior, deployed configuration, or a sequence spanning components. Prefer a narrower test when one component can prove the same contract.

Complete when the test has one named journey, one failure it can discriminate, and a reason browser-level coverage is necessary.