Skip to content

Commit 0921a7d

Browse files
chargomeclaude
andcommitted
test(nextjs): Skip the prerendered ISR assertions on vinext
vinext renders ISR pages for every request, so the trace tags are fresh there and kept, like on the dev server. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
1 parent d3ff875 commit 0921a7d

1 file changed

Lines changed: 6 additions & 2 deletions

File tree

‎dev-packages/e2e-tests/test-applications/nextjs-16/tests/isr-routes.test.ts‎

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,12 @@ import { getSpanOp, waitForStreamedSpan } from '@sentry-internal/test-utils';
44
const isProductionBuild = process.env.TEST_ENV === 'production' || process.env.TEST_ENV === 'prod-turbopack';
55

66
test.describe('prerendered ISR pages', () => {
7-
// The dev server renders ISR pages for every request, so there the trace tags are fresh and kept.
8-
test.skip(!isProductionBuild, 'ISR pages are only prerendered in production builds');
7+
// The dev server and vinext render ISR pages for every request, so there the trace tags are fresh
8+
// and kept.
9+
test.skip(
10+
!isProductionBuild || !!process.env.VINEXT,
11+
'ISR pages are only prerendered by a production build of Next.js',
12+
);
913

1014
test('does not carry trace meta tags on an ISR dynamic route', async ({ page }) => {
1115
// Navigate to ISR page

0 commit comments

Comments
 (0)