Course contentsShow
← React
Lesson 2183 of 2,39648. End-to-End TestingFree lesson

E2E Tests Cover Critical User Journeys

E2E tests should focus on complete workflows like signup, checkout, or core feature flows that matter most to business.

E2E Tests Cover Critical User Journeys

What you'll learn: How to identify and test the most important complete workflows in your React application with E2E tests.

The Core Idea

E2E tests are expensive to write and slow to run, so you can't test everything. Instead, focus on critical user journeys—the complete workflows that represent your application's core value. Think signup → login → purchase, or create account → verify email → complete profile. These are the flows that, if broken, would severely impact your business or user experience.

What Makes a Journey Critical?

A critical user journey is:

  • Revenue-impacting: Checkout, subscription signup, payment processing
  • Core functionality: The main feature your app is built around (e.g., posting content, booking appointments)
  • Frequent user paths: Common workflows that most users experience
  • High-risk areas: Authentication, data submission, critical integrations

The Restaurant Analogy

Imagine testing a restaurant. Unit tests check if the stove works. Integration tests verify the kitchen can prepare dishes. E2E tests ensure a customer can walk in, order, receive food, pay, and leave satisfied. You wouldn't E2E test every possible menu combination—just the most popular dishes and the overall dining experience.

Example Critical Journeys

For an e-commerce React app:

  • Browse products → add to cart → checkout → payment → confirmation
  • User registration → email verification → first purchase
  • Search → filter → product detail → purchase

For a social media app:

  • Sign up → create profile → make first post → receive notifications
  • Login → upload photo → add caption → publish → view in feed

Key Takeaway: E2E tests should cover complete, end-to-end user workflows that matter most to your business goals—not every possible interaction. Focus on the happy paths and critical edge cases that would hurt users or revenue if broken.