Why Noortech Uses Playwright for Next.js Apps

The short version

Playwright is our default end-to-end testing tool for Next.js apps in 2026. Not because Cypress is bad — it isn't — but because Playwright maps better to the actual shape of modern Next.js work: App Router routes, server components, authentication flows, parallel test runs, and CI cost. The choice is pragmatic.

Why we used to reach for Cypress

For a long stretch, Cypress was the obvious default. Cypress popularised the ergonomic test runner, the time-travel debugger, and the “you can see your tests execute” experience that converted thousands of teams from Selenium. For traditional client-side React apps, Cypress is genuinely pleasant to use, and teams that have a mature Cypress codebase have no reason to switch on principle.

Where Cypress starts to bite

Three pain points compound on a Next.js codebase:

• Authentication. Cypress's same-origin policy makes third-party-redirect-based auth (Auth0, Clerk, NextAuth federation) awkward. You end up writing custom programmatic-login plugins and bypassing the actual UI flow you wanted to test.
• Parallel test execution. Cypress's parallelisation requires their paid dashboard or a custom CI harness. Playwright ships parallel sharding natively and works with any CI provider out of the box.
• Multi-tab and multi-context tests. Anything that involves two browser contexts simultaneously (an admin in one tab, a customer in another) is a Playwright strength and a Cypress workaround.

What Playwright does well for Next.js

Playwright was built by ex-Puppeteer engineers at Microsoft with a clear brief: the cross-browser, multi-context, fast-CI test runner that Puppeteer almost was. Five things matter for Next.js teams specifically:

• Auto-waiting that actually works. Playwright's auto-wait is more reliable than Cypress's in our experience — fewer flaky tests on slow CI workers.
• Cross-browser by default. One config, three browsers (Chromium, WebKit, Firefox). For sites that have to ship to iOS Safari, this matters.
• Stateful auth via storage state. Run an auth flow once, save the resulting cookies and localStorage, reuse across thousands of tests. Massive CI-time savings on auth-heavy apps.
• API and UI interleaving. Playwright lets you make raw API calls from inside a test (to seed data, e.g.) without spinning up a separate tool. Cypress can do this via `cy.request`, but Playwright's API surface is cleaner.
• Trace viewer. Playwright's post-mortem trace viewer is genuinely best-in-class. When a test fails on CI, you download the trace and step through it locally with full DOM snapshots and console logs. No more “works on my machine.”

When we'd still use Cypress

If a team already has a thousand passing Cypress tests and a CI pipeline tuned around them, switching to Playwright is rarely worth the migration cost. We respect the sunk-cost reality. For greenfield Next.js work, though, we start with Playwright every time.

How we set Playwright up for a Next.js app

• One config per environment — local, preview, prod. Auth tokens differ; everything else stays consistent.
• Storage-state-based auth. Sign in once, save state, reuse. We run the auth flow itself as a separate spec so it does get test coverage.
• API-seeded test data. Database seeded via a tRPC test endpoint that the app exposes only in non-production environments.
• Sharded CI runs. Playwright's `--shard` flag plus a GitHub Actions matrix gives us 4× speedup at no extra license cost.
• Trace upload on failure. Failed runs upload the trace as a CI artifact. Engineers debug it locally without re-running.

The conclusion

Both Playwright and Cypress are credible choices. Our recommendation for new Next.js work is Playwright, mostly because of auth ergonomics, native parallelisation, and the trace viewer. The pricing structure helps too — Playwright is fully open source and the CI integrations are vendor-neutral. If you're evaluating tooling for a fresh QA setup, Playwright is where we'd start.