Skip to content

Commit 76caa5a

Browse files
authored
chore: add skip entry for renamed e2e test (#2943)
This test suite file was moved in vercel/next.js#77630. This results in it showing up as failed in new reports: https://682e414a03ba12f55c5f417b--runtime-e2e-report.netlify.app/. Example run here: https://github.com/opennextjs/opennextjs-netlify/actions/runs/15163298543#summary-42664185436. I also clarified the `reason` field. We could do something gross to expect the Netlify default 404 page or configure a custom 404 page that mimics Vercel's... but I don't think it's worth it.
1 parent b43474c commit 76caa5a

File tree

1 file changed

+11
-1
lines changed

1 file changed

+11
-1
lines changed

tests/test-config.json

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -199,8 +199,18 @@
199199
]
200200
},
201201
{
202+
"//": "This was the test file name before v15.3.0-canary.27 / v15.3.0",
202203
"file": "test/e2e/basepath.test.ts",
203-
"reason": "Hard-coded Vercel error message",
204+
"reason": "Hard-coded expectation of Vercel's default 404 page",
205+
"tests": [
206+
"basePath should not update URL for a 404",
207+
"basePath should handle 404 urls that start with basePath",
208+
"basePath should show 404 for page not under the /docs prefix"
209+
]
210+
},
211+
{
212+
"file": "test/e2e/basepath/basepath.test.ts",
213+
"reason": "Hard-coded expectation of Vercel's default 404 page",
204214
"tests": [
205215
"basePath should not update URL for a 404",
206216
"basePath should handle 404 urls that start with basePath",

0 commit comments

Comments
 (0)