Situation: A web app has no end-to-end (E2E) tests
Situation: A web app has no end-to-end (E2E) tests.
Solution: Consider writing E2E tests in phases.
Phase 1: Smoke test - Write E2E tests that merely visit each page and assure it loads.
Phase 2: Happy path - Write E2E tests for each feature's "happy path" (the expected, common use case).
Phase 3: Unhappy path - Write E2E tests for edge cases.
Phase 1 is generally easy and provides basic confidence that the app won't blow up when simply navigated. Consider phase 2 or 3 as the team matures.