Are we Next yet?
Next.js deploy tests on Easel

Almost.

99.2% passing

Are we Next yet?

How much of Next.js’s own deploy test suite passes on Easel. Every test app is built, deployed to Easel, tested, and torn down.

Next.js
16.5.0-canary.48
Suite
Deploy e2e
Tests
10,594 cases in 1,255 files
Updated
99.2%of the test cases that run pass on Easel: 4,615 of 4,650. Another 5,944 skip themselves in deploy mode.
Passed 4,615
Failed 35
4,650 test cases ran, 5,944 skipped
Passed
Failed
Test cases that ran, after each run (UTC)

Every test

One cell per test case that ran, file by file. Hover a cell to see which test it is; click it to open its file.

Passed
Failed
Browse all 1,255 test files

What’s measured

Next.js ships an end-to-end test suite with a deploy mode: instead of starting a local server, each test builds its app, deploys it to a hosting provider, and runs its assertions against the deployed URL. Vercel runs the same suite against its own platform.

Here every test app is built with vercel build and deployed to Easel as a prebuilt deployment in a project of its own, then tested and deleted. Functions run on Easel’s own hosts, never on AWS Lambda. Builds use Turbopack and Next.js’s deployment adapter. Tests that Vercel’s own deploy-test manifest excludes are left out here too.

The pass rate counts test cases (each it), from each case’s first attempt with no retries. Cases that skip themselves in deploy mode count toward neither side. On the test files page, a file passes when every case in it that runs passes; 936 of 940 files do.

This run used Next.js 16.5.0-canary.48 against Easel’s platform stack running locally. The numbers come from the tracker the test harness writes after each run, at commit ccda733fc7.