How vinext’s published pass rate is corrected
Arkor’s comparison shows vinext at 95.69%, below the overall rate on vinext’s own page. The difference is one kind of test: an empty one that reports a pass for a suite that never ran.
The counts
From vinext’s run of November 5, 2026, 11:15 JST, on Next.js 16.2.6. The rate at the top of vinext’s page follows its latest run, so it can differ slightly from this one.
| Result | Passed | Failed | Pass rate |
|---|---|---|---|
| Published by vinext | 2,696 | 108 | 96.14% |
| Empty tests | −298 | — | — |
| After correction | 2,398 | 108 | 95.69% |
What is removed
Next.js leaves a suite out of a deployment run with nextTestSetup({ skipDeployment: true }). Its test harness then registers one empty test in the suite’s place, “should skip next deploy”. Jest reports that test as passed, although nothing was checked. vinext’s own workflow calls these “placeholder tests”.
The same rule as Arkor’s
Arkor’s results count a test with this title as skipped, not as passed. Removing it from vinext’s count applies the same rule to both. Nothing else changes: the failures stay as published, and only this exact title is removed.
Check it yourself
vinext publishes each run’s results as artifacts. In the test-results artifacts of this run, 298 passed tests have exactly this title.