Do I need end-to-end testing for a small web app

Not always. For a small web app, you usually do not need a large end-to-end (E2E) test suite.

A practical rule is:

• Unit tests: for logic, helpers, components, validation
• Integration tests: for API + database + key UI flows
• A few E2E tests: only for the most important user journeys

When E2E testing is worth it

Use E2E tests if your app has:

• Critical business flows, like signup, checkout, payments, booking, or publishing
• Multiple moving parts that must work together
• A real risk of regressions in user-facing flows
• A team where catching broken journeys before release matters a lot

When you can skip or minimize it

You can often skip a big E2E suite if:

• The app is small and simple
• Most logic is on the backend or in one place
• You deploy frequently and want fast tests
• Maintaining flaky browser tests would cost more than they help

Good compromise

For a small web app, a common setup is:

• Plenty of unit tests
• Some integration tests
• 1–3 E2E smoke tests for the most important paths

Example E2E smoke tests:

• User can log in
• User can create/save something important
• User can complete the main workflow

Simple recommendation

If you’re early-stage or small team:
Start with unit + integration tests, and add only a few E2E tests for critical flows.
That usually gives the best balance of confidence and maintenance cost.

If you want, I can help you decide based on your app type and suggest a minimal test strategy.