Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Overhaul our tests because our current scaffolding doesn't work with many of the new app-dir tests #2161

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
nickytonline opened this issue Jun 13, 2023 · 3 comments
Assignees
Labels
v4 Issues related to the v4 Next.js runtime

Comments

@nickytonline
Copy link

nickytonline commented Jun 13, 2023

From @orinokai:

we need to overhaul our tests because our current scaffolding doesn't work with many of the new app-dir tests - i think it's important to get a basic level of support shipped and then work on getting these tests in, but shout if you disagree

Originally posted by @orinokai in #2080 (comment)

@orinokai
Copy link
Contributor

Would very much like to overhaul our tests so that we can import the Next e2e tests verbatim, so they are easy to update for future versions. To do this, we'd need to develop a wrapper that can support this.

In addition, it's so important that the tests run faster and more reliably so I'd like to investigate how we could utilize ntl serve instead of actually deploying each site. This would involve bolstering ntl serve itself so it has greater parity with the production environment and will be easier to do if we can reduce our reliance on ODBs for ISR via the new cache-control primitives that are being discussed.

@orinokai
Copy link
Contributor

further to the above, we also need to ensure we have a fast and reliable way to test our Runtime with previous versions of Next

@orinokai orinokai self-assigned this Jul 5, 2023
@MarcL MarcL added v4 Issues related to the v4 Next.js runtime and removed Ecosystem: Frameworks labels Mar 13, 2024
@MarcL
Copy link
Contributor

MarcL commented Apr 23, 2024

Closing this as we're now using v5 runtime which has expanded test coverage.

@MarcL MarcL closed this as completed Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v4 Issues related to the v4 Next.js runtime
Projects
None yet
Development

No branches or pull requests

3 participants