Cypress for End-to-End Testing in Next.js

Why it exists

Unit tests confirm a function returns the right value. They cannot confirm that clicking Add to Cart on a real rendered page actually updates the visible cart count, because no browser is involved. Cypress exists to close that gap, it drives an actual browser through the same paths a user would take, catching integration failures that unit tests structurally cannot see, whether the app is built with Next.js, plain React, or anything else browser based.

The mental model

Cypress is not a remote control operating a browser from outside, the way Selenium or Playwright typically work. It runs inside the browser, in the same run loop as your application, using a Node process alongside it to reach outside the sandbox when needed. That proximity is why it can automatically wait for elements to appear, retry assertions until they pass or time out, and offer time travel debugging, letting you hover over any past test step and see the DOM exactly as it was at that moment.

How it works

You write tests in JavaScript or TypeScript describing user journeys, visit a route, type into a field, click a button, assert the result. Cypress launches a real browser, mounts your Next.js app, either the dev server or a production build, and executes each command against the live DOM, automatically retrying queries for a few seconds before failing, which absorbs most flakiness from asynchronous rendering and data fetching. Next.js documents Cypress configuration directly for both the App Router and Pages Router, including handling client and server components in the same test run.

When it matters

Reach for Cypress when a flow crosses multiple components and real browser behavior, checkout, authentication redirects, form validation, not when testing a single pure function, which belongs in Jest or Vitest instead. The footgun is over testing, writing dozens of slow, brittle end to end specs for logic that a five line unit test would cover in milliseconds, which turns a CI pipeline into a bottleneck nobody wants to run locally.

A concrete example

A Next.js e-commerce app has a Cypress spec that visits a product page, clicks Add to Cart, then asserts the cart icon badge shows one and a toast reads Added to cart. If the App Router server component fetches stale inventory data, or a client component fails to re-render the badge, the test fails exactly where a real shopper would notice, which a component level unit test would likely have missed entirely.